Thanks everyone, I think we've managed to clear up the confusion. We might go
via Kerberos however. But thanks for the help.
John
Information in this email including any attachments may be privileged,
confidential and is intended exclusively for the addressee. The views expressed
may not be off
Note that the SSL username is the subject of the client certificate -
without client certs you don't get custom usernames.
On Wed, Apr 20, 2016 at 2:39 PM, Harsh J wrote:
> Username would need to come in from the authentication layer.
>
> What is your choice of authentication mode? Based on SSL
Username would need to come in from the authentication layer.
What is your choice of authentication mode? Based on SSL vs. Kerberos,
you'll need to configure the clients per
http://kafka.apache.org/documentation.html#security_configclients (SSL)
which requires using a configuration properties file
John,
Setup SASL using the username match you set on ACL will work for your case.
you can follow the steps in offical document.
Ping
On Wed, Apr 20, 2016 at 6:08 AM, Pawley, John wrote:
> Hello,
>
> We have managed to enable the SimpleAuthorizer for Kafka, and we can no
> longer connect to the
Hello,
We have managed to enable the SimpleAuthorizer for Kafka, and we can no longer
connect to the local queue without authorization. However we can't figure out
how to supply a username when trying to connect from the console producer. We
have already added users with permissions via the kaf
