🔒 Enable SSL listeners for Kafka Brokers #70
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes the following use case to resolve #63
[:heavy_check_mark:] Enable SSL listener
[:heavy_check_mark:] Use of server keystore, truststore to expose SSL endpoint
[:heavy_check_mark:] No authentication required
[:heavy_check_mark:] Use of client truststore to connect to the Kafka SSL endpoint
[:heavy_check_mark:] Enable SASL (PLAIN mechanism) authentication under the SSL listener
[:heavy_check_mark:] Enable SASL (SCRAM mechanism) authentication under the SSL listener
[:red_circle:] Enable TLS authentication under the SSL listener
The
amq_streams_ssl_no_auth.yml
playbook tests and verifies the no authentication use case.The
amq_streams_ssl_auth_sasl.yml
playbook tests and verifies the authentication use cases.The playbooks require the use of a set of keystore and truststore files, all of them created for testing purposes in the folder cerst.
This PR is in Work-in-Progess and it is not ready for review or merge. It is pending of the following actions: