STORM-4079: Add SSL setup documentation#8428
Conversation
rzo1
left a comment
rzo1
left a comment
There was a problem hiding this comment.
All of the mentioned properties do not exist. Please verify any changes (generated by generative AI).
rzo1
left a comment
rzo1
left a comment
There was a problem hiding this comment.
Thanks for updating. Overall, I am wondering what the actual goal of this change is? I think the documenation as noted in the related issue lacks information on how to configure STorm to communicate over SSL/TLS (or mTLS) as implemented in https://issues.apache.org/jira/browse/STORM-4075.
That means we would need to update the docs to mention the config properties as described in the related PR: https://github.com/apache/storm/pull/3692/changes
The actual changes for normal SSL/LTS are already included: https://github.com/apache/storm/pull/8072/changes
| For UI users needs to set following config in storm.yaml. Generating keystores with proper keys and certs should be taken care by the user before this step. | ||
|
|
||
| 1. ui.https.port | ||
| 1. ui.https.port (Port for HTTPS UI access) |
There was a problem hiding this comment.
I think this change can be removed since it is obvious.
| </dependencySet> | ||
| </dependencySets> | ||
|
|
||
| <files> |
There was a problem hiding this comment.
These changes do nto belong to STORM-4079 and should be removed.
|
Thanks for the clarification. I have added an overview explaining how TLS configuration works for internal communication using the existing configuration properties. Please let me know if any further improvements are needed. |
|
Thx |
3 participants
What is the purpose of the change
This PR adds documentation explaining how to configure SSL in Apache Storm.
It provides clear guidance for users who want to secure their Storm cluster communication.
The documentation explains the process of enabling SSL and configuring the required
security components.
The documentation includes:
How was the change tested
The documentation was reviewed to ensure the configuration steps and commands are accurate
and consistent with the current Apache Storm configuration options. Since this change only
adds documentation and does not modify runtime code, no additional functional tests were required.