chia7712 commented on code in PR #23818:
URL: https://github.com/apache/kafka/pull/23818#discussion_r4294040680
##########
docs/security/authentication-using-sasl.md:
##########
@@ -503,6 +503,31 @@ The OAUTHBEARER broker configuration includes:
* sasl.oauthbearer.jwks.endpoint.url
* sasl.oauthbearer.scope.claim.name
* sasl.oauthbearer.sub.claim.name
+
+##### Tokenless login for validate-only brokers
+
+A broker may only validate OAUTHBEARER tokens presented by clients and use a
different SASL mechanism (or a different listener) for inter-broker
communication. Such a broker never needs to obtain a token of its own, but it
still performs a JAAS login with `OAuthBearerLoginModule` for the OAUTHBEARER
listener at startup.
+
+If `sasl.login.callback.handler.class` is not set for the listener, the login
uses the default `OAuthBearerUnsecuredLoginCallbackHandler`. When none of the
JAAS module options start with `unsecuredLogin`, this handler does not create a
token; the login succeeds without a token (a tokenless login), and the broker
logs that this login cannot be used to establish client connections. JAAS
module options that are not related to unsecured token creation, such as the
`ssl.*` options used to configure TLS trust for an `https` JWKS endpoint, do
not change this. For example:
+
+```java-properties
+listeners=SASL_SSL://host.name:port
+security.inter.broker.protocol=SSL
Review Comment:
Does it work if the `listeners` don't have `SSL` ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]