You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Gabor Somogyi (JIRA)" <ji...@apache.org> on 2018/11/27 10:53:00 UTC
[jira] [Updated] (KAFKA-7677) Client login with already existing
JVM subject
[ https://issues.apache.org/jira/browse/KAFKA-7677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gabor Somogyi updated KAFKA-7677:
---------------------------------
Affects Version/s: 2.2.0
> Client login with already existing JVM subject
> ----------------------------------------------
>
> Key: KAFKA-7677
> URL: https://issues.apache.org/jira/browse/KAFKA-7677
> Project: Kafka
> Issue Type: New Feature
> Affects Versions: 2.2.0
> Reporter: Gabor Somogyi
> Priority: Major
>
> If JVM is already logged in to KDC and has a Subject + TGT in it's security context it can be used by clients and not logging in again. Example code:
> {code:java}
> org.apache.hadoop.security.UserGroupInformation.getCurrentUser().doAs(
> new java.security.PrivilegedExceptionAction[Unit] {
> override def run(): Unit = {
> val subject = javax.security.auth.Subject.getSubject(java.security.AccessController.getContext())
> val adminClient = AdminClient.create...
> }
> )
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)