Ensure ZooKeeper Authentication Credentials Have Been Changed

CritiqueNiveau 1Revue manuelletdsql

Description

TDSQL uses digest authentication to connect to ZooKeeper. The initial credentials used during installation should be uniformly changed to strong random values by the deployment side before production and stored encrypted.

Méthode de vérification

Méthode d'audit: Revue manuelle

Cette recommandation ne peut pas être vérifiée automatiquement. Une analyse la liste avec ces instructions lorsque vous passez --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)

Méthode de correction

Méthode de correction: Recommandation ou correctif d'infrastructure

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;

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: tdsqlzookeepercredentials
Référence: CIS Tencent TDSQL 10.3.22 Benchmark v1.0.0 - 11.2 Ensure ZooKeeper Authentication Credentials Have Been Changed