[
https://issues.apache.org/jira/browse/KAFKA-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424443#comment-15424443
]
ASF GitHub Bot commented on KAFKA-3492:
---------------------------------------
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/1753
KAFKA-3492: Secure quotas for authenticated users
Implementation and tests for secure quotas at <user> and <user, client-id>
levels as described in KIP-55. Also adds dynamic default quotas for
<client-id>, <user> and <user-client-id>. For each client connection, the most
specific quota matching the connection is used, with user quota taking
precedence over client-id quota.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-3492
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1753.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1753
----
----
> 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)
