[ https://issues.apache.org/jira/browse/KAFKA-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004864#comment-15004864 ]
ASF GitHub Bot commented on KAFKA-2838: --------------------------------------- GitHub user Parth-Brahmbhatt opened a pull request: https://github.com/apache/kafka/pull/529 KAFKA-2838: Allow comma in super users, allow comma in CLI authz prop… …erties. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Parth-Brahmbhatt/kafka KAFKA-2838 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/529.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 #529 ---- commit b7b7874dc401e2498b00fae3ab9fb1018d45e572 Author: Parth Brahmbhatt <brahmbhatt.pa...@gmail.com> Date: 2015-11-13T23:02:10Z KAFKA-2838: Allow comma in super users, allow comma in CLI authz properties. ---- > allow comma when specifying superusers > -------------------------------------- > > Key: KAFKA-2838 > URL: https://issues.apache.org/jira/browse/KAFKA-2838 > Project: Kafka > Issue Type: Bug > Reporter: Jun Rao > Fix For: 0.9.0.0 > > > Currently, super users are specified in csv as the following. > super.users=User:Bob,User:Alice > However, if a super user is based on ssl peer principal, it may have comma in > the user name like the following. > CN=writeuser,OU=Unknown,O=Unknown,L=Unknown,ST=Unknown,C=Unknown > Then, we won't be able to parse the value properly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)