[
https://issues.apache.org/jira/browse/KAFKA-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629247#comment-16629247
]
ASF GitHub Bot commented on KAFKA-7429:
---------------------------------------
rajinisivaram opened a new pull request #5699: KAFKA-7429: Enable
key/truststore update with same filename/password
URL: https://github.com/apache/kafka/pull/5699
Reload SSL trust stores and keystores on AlterConfigsRequest from the admin
client if the file was modified, even if the file name and password haven't
changed.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Enable dynamic key/truststore update with same filename/password
> ----------------------------------------------------------------
>
> Key: KAFKA-7429
> URL: https://issues.apache.org/jira/browse/KAFKA-7429
> Project: Kafka
> Issue Type: Improvement
> Components: security
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Priority: Major
> Fix For: 2.1.0
>
>
> At the moment, SSL keystores and truststores on brokers can be dynamically
> updated using AdminClient by providing a new keystore or truststore. But we
> require either the filename or password to be modified to trigger the update.
> In some scenarios, we may want to perform the update using the same file (and
> password). So it will be good to provide a way to trigger reload of existing
> keystores and truststores using the same AdminClient update mechanism.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
