zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koontz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-938) Support Kerberos authentication of clients.
Date Tue, 09 Aug 2011 19:36:27 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081866#comment-13081866
] 

Eugene Koontz commented on ZOOKEEPER-938:
-----------------------------------------

Hi Benjamin, 
Thanks a lot for your feedback! I addressed the two cleanup issues in a new patch. 

Regarding the sun.* classes, these are only needed to determine the default Kerberos realm
from the system's Kerberos conf file (usually in /etc/krb5.conf). 

I think we can use the java.security.* functionality to replace sun.security.*:  
 http://download.oracle.com/javase/1.4.2/docs/guide/security/jgss/tutorials/KerberosReq.html

I will try this out and update the patch if this will work.

> Support Kerberos authentication of clients.
> -------------------------------------------
>
>                 Key: ZOOKEEPER-938
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-938
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: java client, server
>            Reporter: Eugene Koontz
>            Assignee: Eugene Koontz
>             Fix For: 3.4.0, 3.5.0
>
>         Attachments: NIOServerCnxn.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch,
ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch,
ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch,
jaas.conf, sasl.patch
>
>
> Support Kerberos authentication of clients. 
> The following usage would let an admin use Kerberos authentication to assign ACLs to
authenticated clients.
> 1. Admin logs into zookeeper (not necessarily through Kerberos however). 
> 2. Admin decides that a new node called '/mynode' should be owned by the user 'zkclient'
and have full permissions on this.
> 3. Admin does: zk> create /mynode content sasl:zkclient@FOOFERS.ORG:cdrwa
> 4. User 'zkclient' logins to kerberos using the command line utility 'kinit'.
> 5. User connects to zookeeper server using a Kerberos-enabled version of zkClient (ZookeeperMain).
> 6. Behind the scenes, the client and server exchange authentication information. User
is now authenticated as 'zkclient'.
> 7. User accesses /mynode with permissions 'cdrwa'.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message