You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Viktor Somogyi-Vass (Jira)" <ji...@apache.org> on 2023/07/19 14:24:00 UTC
[jira] [Commented] (KAFKA-8128) Dynamic delegation token change possibility for consumer/producer
[ https://issues.apache.org/jira/browse/KAFKA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744640#comment-17744640 ]
Viktor Somogyi-Vass commented on KAFKA-8128:
--------------------------------------------
So after 4 years (yes) I think I'll pick this up. The problem came up more recently with OAuth but I believe the core problem here that JAAS contexts won't get reloaded. Making it a dynamic configuration would solve it but that probably requires a KIP too. I'll see what's up.
[~gsomogyi] does this seem correct? Did you have problems because you had to change the JAAS config or were there any other problems that you experienced?
> 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)