[
https://issues.apache.org/jira/browse/KAFKA-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viktor Somogyi-Vass updated KAFKA-8128:
---------------------------------------
Description:
Clients using JAAS based authentication are now forced to restart themselves in
order to reload the JAAS configuration. We could
- make the {{sasl.jaas.config}} dynamically configurable and therefore better
equip them to changing tokens etc.
- detect file system level changes in configured JAAS and reload the context.
Original issue:
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.
was: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.
> Dynamic JAAS change for clients
> -------------------------------
>
> 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
>
> Clients using JAAS based authentication are now forced to restart themselves
> in order to reload the JAAS configuration. We could
> - make the {{sasl.jaas.config}} dynamically configurable and therefore better
> equip them to changing tokens etc.
> - detect file system level changes in configured JAAS and reload the context.
> Original issue:
> 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)
