You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2025/06/16 15:40:00 UTC

[jira] [Created] (ZOOKEEPER-4938) Allow specifying LoginContext directly

Istvan Toth created ZOOKEEPER-4938:
--------------------------------------

             Summary: Allow specifying LoginContext directly
                 Key: ZOOKEEPER-4938
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4938
             Project: ZooKeeper
          Issue Type: New Feature
          Components: kerberos
            Reporter: Istvan Toth


Currently ZK allows setting the Application name, but always uses the global javax.security.auth.login.Configuration object to retirieve it.

Some applications (notably anything using the Hadoop UserGroupInformation) create and set their own LoginContext object.

For these cases, the user somehow needs to duplicate the required jaas Configuration, and install it globally (either creating a _jaas.conf_ file and setting the_java.security.auth.login.config_ system property, or by programmatically installing a Configuration object)

Life would be MUCH easier if ZK allowed directly setting the LoginContext object for, so that applications can set the SASLconfig  without having to override the global Configuration.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)