Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add per-listener connections.max.reauth.ms support
See original GitHub issueApache Kafka provides the connections.max.reauth.ms [1] configuration parameter which can be set at broker level so applied on all listeners or even on a specific listener only.
Currently, Strimzi doesn’t have support for specifying such a parameter at listener level because the listener. prefix is part of the list of the forbidden ones for the spec.kafka.config section.
The connections.max.reauth.ms would make sense for OAuth and SCRAM authentications enabled on a specific listener so we should add support in the authentication section of listeners via the KafkaListenerAuthenticationOAuth and KafkaListenerAuthenticationScramSha512 classes adding a new field for it.
[1] https://kafka.apache.org/documentation/#brokerconfigs_connections.max.reauth.ms
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
(For
type: customauthentication, I guess it can be already configured: https://github.com/strimzi/proposals/blob/1e6b49e5e6cbb001dff7adf2c3e3ec892487d2b7/032-custom_authentication_in_kafka_brokers.md?plain=1#L76)Triaged on 26.5.2022: There seem to be a different opinions on how the API should look like. So maybe we sould have a proposal to clarify all the concerns and alternatives.