[
https://issues.apache.org/jira/browse/KAFKA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749087#comment-17749087
]
Gabor Somogyi commented on KAFKA-8128:
--------------------------------------
It took some time to remember what was the original issue since the jira
reporter not written it down clearly😅
Now I remember that JAAS context is definitely not re-loaded which is the root
cause. As I remember there is a manual JAAS context reload possibility in the
JVM but it didn't have effect on the producer/consumer. The last statement may
or may not be valid since it was 4 years ago...
All in all it would be good to have an explicit API to change the token which
would solve many issues for sure.
> Dynamic delegation token change possibility for consumer/producer
> -----------------------------------------------------------------
>
> Key: KAFKA-8128
> URL: https://issues.apache.org/jira/browse/KAFKA-8128
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 2.2.0
> Reporter: Gabor Somogyi
> Assignee: Viktor Somogyi-Vass
> Priority: Major
>
> Re-authentication feature on broker side is under implementation which will
> enforce consumer/producer instances to re-authenticate time to time. It would
> be good to set the latest delegation token dynamically and not re-creating
> consumer/producer instances.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
