[
https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043552#comment-16043552
]
ASF GitHub Bot commented on KAFKA-3199:
---------------------------------------
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
----
> LoginManager should allow using an existing Subject
> ---------------------------------------------------
>
> Key: KAFKA-3199
> URL: https://issues.apache.org/jira/browse/KAFKA-3199
> Project: Kafka
> Issue Type: Improvement
> Components: security
> Affects Versions: 0.9.0.0
> Reporter: Adam Kunicki
> Assignee: Adam Kunicki
> Priority: Critical
>
> LoginManager currently creates a new Login in the constructor which then
> performs a login and starts a ticket renewal thread. The problem here is that
> because Kafka performs its own login, it doesn't offer the ability to re-use
> an existing subject that's already managed by the client application.
> The goal of LoginManager appears to be to be able to return a valid Subject.
> It would be a simple fix to have LoginManager.acquireLoginManager() check for
> a new config e.g. kerberos.use.existing.subject.
> This would instead of creating a new Login in the constructor simply call
> Subject.getSubject(AccessController.getContext()); to use the already logged
> in Subject.
> This is also doable without introducing a new configuration and simply
> checking if there is already a valid Subject available, but I think it may be
> preferable to require that users explicitly request this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
