hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laxman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4791) Allow Secure Zookeeper JAAS configuration to be programmatically set (rather than only by reading JAAS configuration file)
Date Mon, 18 Jun 2012 04:55:43 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13393665#comment-13393665

Laxman commented on HBASE-4791:

@Matt, "zookeeper.sasl.clientconfig" is only for client context name. Basically, in a JAAS
configuration we can have multiple sections like below one.

Client {       
com.sun.security.auth.module.Krb5LoginModule required

ZOOKEEPER-1373 enables the user to configure a specific section from JAAS to be used for zookeeper
and *it still requires the configuration "java.security.auth.login.config"*. But, current
jira is mainly for allowing the JAAS can be configured via programmatically and avoid configuring
via system property. So, this requires changes on zookeeper like allowing client to provide
a config object or so...

Correct me if my understanding is wrong.
> Allow Secure Zookeeper JAAS configuration to be programmatically set (rather than only
by reading JAAS configuration file)
> --------------------------------------------------------------------------------------------------------------------------
>                 Key: HBASE-4791
>                 URL: https://issues.apache.org/jira/browse/HBASE-4791
>             Project: HBase
>          Issue Type: Improvement
>          Components: security, zookeeper
>            Reporter: Eugene Koontz
>            Assignee: Eugene Koontz
>              Labels: security, zookeeper
>         Attachments: HBASE-4791-v0.patch
> In the currently proposed fix for HBASE-2418, there must be a JAAS file specified in
> However, it might be preferable to construct a JAAS configuration programmatically, as
is done with secure Hadoop (see https://github.com/apache/hadoop-common/blob/a48eceb62c9b5c1a5d71ee2945d9eea2ed62527b/src/java/org/apache/hadoop/security/UserGroupInformation.java#L175).
> This would have the benefit of avoiding a usage of a system property setting, and allow
instead an HBase-local configuration setting.	

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message