[ZOOKEEPER-1811] The ZooKeeperSaslClient service name principal is hardcoded to "zookeeper"

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.5
• Fix Version/s: 3.4.6, 3.5.0
• Component/s: java client
• Hadoop Flags: Reviewed

Release Note

Adds a new system property "zookeeper.sasl.client.username" that can be used to configure the ZK Kerberos (SASL) client user principal name to something other than "zookeeper" (default) for any environments that use non-standard naming for its principals.

• Assignee: Harsh J
• Reporter: Harsh J
• Created: 07/Nov/13 05:37
• Updated: 23/Jul/15 18:54
• Resolved: 10/Feb/14 21:33

Description

The ClientCnxn class in ZK instantiates the ZooKeeperSaslClient with a hardcoded service name of "zookeeper". This causes all apps to fail in accessing ZK in a secure environment where the administrator has changed the principal name ZooKeeper runs as.

The service name should be configurable.

Issue Links

• relates to: AMBARI-12347 AMS does not work with Kerberization in distrbuted mode