kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-2858) Clarify usage of `Principal` in the authentication layer
Date Fri, 10 Nov 2017 09:46:01 GMT

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

ASF GitHub Bot commented on KAFKA-2858:
---------------------------------------

Github user ijuma closed the pull request at:

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


> Clarify usage of `Principal` in the authentication layer
> --------------------------------------------------------
>
>                 Key: KAFKA-2858
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2858
>             Project: Kafka
>          Issue Type: Improvement
>          Components: security
>            Reporter: Ismael Juma
>            Assignee: Ismael Juma
>            Priority: Minor
>
> We currently use `KafkaPrincipal` at the authentication and authorization layer. But
there is an implicit assumption that we always use a `KafkaPrincipal` with principalType ==
USER_TYPE as we ignore the the principalType of the `KafkaPrincipal` when we create `RequestChannel.Session`.
> I think it would be clearer if we used a separate `Principal` implementation in the authentication
layer.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message