kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sriharsha Chintalapani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject
Date Thu, 01 Sep 2016 18:20:20 GMT

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

Sriharsha Chintalapani commented on KAFKA-3199:

[~tucu00] HADOOP-13558 is not relevant here. We don't accept the subjects that comes from
host application and there is no such provision. A client will initiate the LoginManager and
will take care of the life cycle of the 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:
>            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

View raw message