You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Rajini Sivaram (JIRA)" <ji...@apache.org> on 2016/04/18 17:50:25 UTC

[jira] [Updated] (KAFKA-3492) support quota based on authenticated user name

     [ https://issues.apache.org/jira/browse/KAFKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajini Sivaram updated KAFKA-3492:
----------------------------------
    Description: 
Currently, quota is based on the client.id set in the client configuration, which can be changed easily. Ideally, quota should be set on the authenticated user name. We will need to have a KIP proposal/discussion on this first.

Details are in KIP-55: https://cwiki.apache.org/confluence/display/KAFKA/KIP-55%3A+Secure+Quotas+for+Authenticated+Users

  was:Currently, quota is based on the client.id set in the client configuration, which can be changed easily. Ideally, quota should be set on the authenticated user name. We will need to have a KIP proposal/discussion on this first.


> support quota based on authenticated user name
> ----------------------------------------------
>
>                 Key: KAFKA-3492
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3492
>             Project: Kafka
>          Issue Type: New Feature
>          Components: core
>            Reporter: Jun Rao
>            Assignee: Rajini Sivaram
>
> Currently, quota is based on the client.id set in the client configuration, which can be changed easily. Ideally, quota should be set on the authenticated user name. We will need to have a KIP proposal/discussion on this first.
> Details are in KIP-55: https://cwiki.apache.org/confluence/display/KAFKA/KIP-55%3A+Secure+Quotas+for+Authenticated+Users



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)