[
https://issues.apache.org/jira/browse/KAFKA-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-2849:
-------------------------------
Resolution: Not A Problem
Fix Version/s: (was: 0.9.0.0)
Status: Resolved (was: Patch Available)
It turns out that this is intentional. Part of the confusion is that the
authenticator implementations are returning `KafkaPrincipal` so I thought we
were losing the principal type in `RequestChannel.Session`. But, in fact, the
authenticator implementations always return KafkaPrincipal instances with
principal type of USER_TYPE. I think it would be clearer if we don't use
`KafkaPrincipal` in `Authenticator` implementations. I will file a separate
issue about that.
> Pass `KafkaChannel.principal` to `RequestChannel.Session`
> ---------------------------------------------------------
>
> Key: KAFKA-2849
> URL: https://issues.apache.org/jira/browse/KAFKA-2849
> Project: Kafka
> Issue Type: Bug
> Components: security
> Reporter: Ismael Juma
> Assignee: Ismael Juma
>
> The current code does:
> {code}
> val session = RequestChannel.Session(new
> KafkaPrincipal(KafkaPrincipal.USER_TYPE, channel.principal().getName),
> channel.socketDescription)
> {code}
> It looks to me like we should just pass `channel.principal`.
> cc [~parth.brahmbhatt]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
