[
https://issues.apache.org/jira/browse/KAFKA-21221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123620#comment-18123620
]
Chia-Ping Tsai commented on KAFKA-21221:
----------------------------------------
Another option is to change the channel builder so that it skips login for
listeners that do not need a token (non inter-broker listeners). However, that
is a much bigger behavior change: custom login modules and callback handlers
may rely on login being invoked
> Add tokenless OAuth login class
> -------------------------------
>
> Key: KAFKA-21221
> URL: https://issues.apache.org/jira/browse/KAFKA-21221
> Project: Kafka
> Issue Type: Improvement
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Minor
>
> KAFKA-21143 showcases a real use case: a broker that only validates incoming
> OAUTHBEARER tokens (inter-broker uses another mechanism) does not need a
> token of its own. Today the only way to get a tokenless login is to rely on
> the default OAuthBearerUnsecuredLoginCallbackHandler, which is documented as
> testing-only. The fix for KAFKA-21143 repairs that default path, but
> production users still deserve a dedicated, documented class that skips token
> retrieval.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)