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

Posted to dev@kafka.apache.org by utenakr <gi...@git.apache.org> on 2017/06/08 22:35:34 UTC

[GitHub] kafka pull request #3274: KAFKA-3199 LoginManager should allow using an exis...

GitHub user utenakr opened a pull request:

    https://github.com/apache/kafka/pull/3274

    KAFKA-3199 LoginManager should allow using an existing Subject

    LoginManager or KerberosLogin (for > kafka 0.10) should allow using an existing Subject. If there's an existing subject, the Jaas configuration won't needed in getService()

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/utenakr/kafka trunk

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/3274.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3274
    
----
commit 95d6b98440f02fee23f8063ad082ec3dae4bd0b2
Author: Ji Sun <ji...@streamsets.com>
Date:   2017-06-08T22:21:50Z

    KAFKA-3199 LoginManager should allow using an existing Subject

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---