-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add trustStore and needClientAuth config to yaml (#834) #1118
Conversation
peeking at that test failure.. sorted! |
if it helps, for some context, the yaml for this use case is produced at: https://github.com/gtully/activemq-artemis-operator/blob/_jmx_exporter_agent/controllers/activemqartemis_reconciler.go#L2096 |
...tion_tests/src/test/java/io/prometheus/jmx/test/http/ssl/SSLWithTrustStoreAndClientAuth.java
Outdated
Show resolved
Hide resolved
...tion_tests/src/test/java/io/prometheus/jmx/test/http/ssl/SSLWithTrustStoreAndClientAuth.java
Outdated
Show resolved
Hide resolved
...tion_tests/src/test/java/io/prometheus/jmx/test/http/ssl/SSLWithTrustStoreAndClientAuth.java
Outdated
Show resolved
Hide resolved
@dhoard thanks for the review, much appreciated. |
@gtully Initial comments...
Usage
|
Signed-off-by: Gary Tully <[email protected]>
@dhoard sure, mutualTLS works too and is more high level, thanks. |
Updated copyright year Signed-off-by: Doug Hoard <[email protected]>
@gtully looks good! Thanks again for the PR!!! |
@dhoard I am making use of the custom authenticator and want to grant permissions based on the clients certificate so I need to be able to configure needClientAuth on the ssl parameters. Also, in kube land, I need to be able to configure the key and trust store types to support PEM key stores. Having these exposed in the yaml config leaves the system properties free for others.
From what I understand, this additional truststore config will also help with #834