Chia-Ping Tsai created KAFKA-21294:
--------------------------------------
Summary: The example of "Configuring Production Kafka Brokers"
does not work since the login callback is missing
Key: KAFKA-21294
URL: https://issues.apache.org/jira/browse/KAFKA-21294
Project: Kafka
Issue Type: Bug
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai
{code:java}
3. Configure SASL port and SASL mechanisms in server.properties as described
here. For example: ```java-properties
listeners=SASL_SSL://host.name:port
security.inter.broker.protocol=SASL_SSL
sasl.mechanism.inter.broker.protocol=OAUTHBEARER
sasl.enabled.mechanisms=OAUTHBEARER
listener.name.<listener
name>.oauthbearer.sasl.server.callback.handler.class=org.apache.kafka.common.security.oauthbearer.OAuthBearerValidatorCallbackHandler
listener.name.<listener
name>.oauthbearer.sasl.oauthbearer.jwks.endpoint.url=https://example.com/oauth2/v1/keys
listener.name.<listener
name>.oauthbearer.sasl.oauthbearer.expected.audience=my-kafka-cluster
listener.name.<listener
name>.oauthbearer.sasl.oauthbearer.expected.issuer=https://example.com
``` {code}
The internal communication is using OAUTHBEARER, but it doesn't set the login
callback. Hence, the broker won't have the token, which results in failure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
