Not necessarily "admin" any name is ok, we use the CN stored in the keystore, but we don't use sasl, and that's how the brokers communicate to each other. You need some way of allowing them to communicate.
On Wed, Jun 1, 2016 at 10:33 AM Rajini Sivaram <rajinisiva...@googlemail.com> wrote: > The server configuration in > > http://stackoverflow.com/questions/37536259/broker-replication-error-not-authorized-to-access-topics-topic-authorization > specifies security.inter.broker.protocol=PLAINTEXT. This would result in > the principal "anonymous" to be used for inter-broker communication. Looks > like you are expecting to use the username "admin" for the broker, so you > should set security.inter.broker.protocol=SASL_PLAINTEXT. There is also a > missing entry in the KafkaServer section of jaas.conf. You need to add > user_admin="welcome1". > > Hope that helps. > > On Wed, Jun 1, 2016 at 7:23 AM, Gerard Klijs <gerard.kl...@dizzit.com> > wrote: > > > What do you have configured, do you have the brokers set as super users, > > with the right certificate? > > > > On Wed, Jun 1, 2016 at 6:43 AM 换个头像 <guoxu1...@foxmail.com> wrote: > > > > > Hi Kafka Experts, > > > > > > > > > I setup a secured kafka cluster(slal-plain authentication). But when I > > try > > > to add ACLs for some existing topics, all three brokers output errors > > like > > > "Not authorized to access topics: [Topic authorization failed.]". > > > > > > > > > I checked my configuration several times according to official > > > document(security section), but still not able to figure out why this > > error > > > caused. > > > > > > > > > Please help. > > > > > > > > > Broker replication error “Not authorized to access topics: [Topic > > > authorization failed.] ” > > > > > > > > > http://stackoverflow.com/questions/37536259/broker-replication-error-not-authorized-to-access-topics-topic-authorization > > > > > > > > > Regards > > > Shawn > > > > > > -- > Regards, > > Rajini >
