Ensure ZooKeeper Authentication Credentials Have Been Changed

Como é verificado

Método de auditoria: Revisão manual

Esta recomendação não pode ser verificada automaticamente. Uma varredura a lista com estas instruções quando você passa --include-manual.

# 1. Attempt to access a key ZNode via zkCli as an unauthorized identity (should be denied) zkCli.sh -server <zk_ip>:<port> ls /tdsql # Expected: Authentication is not valid # 2. Compare the deployed ZK authentication credentials against the install template's initial values; they must differ # (The exact location depends on the deployment form: centralized deployment uses scheduler.xml; TCE deployment uses the tdsql_install template)

Como é corrigido

Método de correção: Orientação ou patch de infraestrutura

1. Generate a new strong random password (>= 16 characters including uppercase, lowercase, digits, and special characters). 2. Batch-update the ZK authentication configuration of all TDSQL components (OSS, Manager, Scheduler, Keeper, Agent, Proxy) via the deployment tool. 3. Re-setAcl existing ZNodes to apply the new credentials. 4. Enable ACL mode (see Recommendation 10.1). Note: This operation requires updating all components simultaneously;