[ZOOKEEPER-1420] Kerberos principal to user mapping / authorization

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.4.0
• Component/s: server
• Assignee: Unassigned
• Reporter: Thomas Weise
• Created: 16/Mar/12 01:21
• Updated: 17/May/12 18:41

Description

ZOOKEEPER-938 introduces server configuration options to perform a rudimentary mapping from Kerberos principal to user name:

kerberos.removeHostFromPrincipal
kerberos.removeRealmFromPrincipal

Those are sufficient to make things work for HBase and other server clusters where we cannot include the host name portion into the znode ACL, but it would be better to support a more standard approach to perform the mapping with finer grained control (i.e. do this only for specific matching principals).

Mapping in Hadoop: https://ccp.cloudera.com/display/CDHDOC/Appendix+C+-+Configuring+the+Mapping+from+Kerberos+Principals+to+Short+Names

As an alternative, a matching option at the time of ACL check that can be controlled by the process assigning ACLs to znodes could also serve the purpose. For example, principals:

user/[e-mail]
user/[e-mail]

would have access to a znode with ACL set as:

sasl:user/host*@TEST.DOMAIN:cdrwa

This would not require ZK server configuration, but add more runtime overhead.

Issue Links

• is related to: ZOOKEEPER-938 Support Kerberos authentication of clients.
• is related to: ZOOKEEPER-1467 Make server principal configurable at client side.