Skip to content
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

How to activate AMQ_WEBKEYSTOREPW and AMQ_WEBTRUSTSTOREREF ? #542

Closed
JBarbes opened this issue Oct 26, 2023 · 1 comment
Closed

How to activate AMQ_WEBKEYSTOREPW and AMQ_WEBTRUSTSTOREREF ? #542

JBarbes opened this issue Oct 26, 2023 · 1 comment

Comments

@JBarbes
Copy link

JBarbes commented Oct 26, 2023

Hi
During image build a version of tls.xml is configured with contents like this:

"
<keyStore id="MQWebTrustStore" location="/run/runmqserver/tls/trust.p12" type="PKCS12" password="${env.AMQ_WEBKEYSTOREPW}" /
<ssl id="thisSSLConfig" clientAuthenticationSupported="true" keyStoreRef="MQWebKeyStore" trustStoreRef="${env.AMQ_WEBTRUSTSTOREREF}" sslProtocol="TLSv1.2"/
"

I would like to use truststore trust.p12, but it seems that AMQ_WEBKEYSTOREPW and AMQ_WEBTRUSTSTOREREF are not set by default.
How do I do that?

@JBarbes JBarbes closed this as completed Oct 31, 2023
@JBarbes
Copy link
Author

JBarbes commented Oct 31, 2023

Ahh - now I know how it works.
I did know how go-worked, and that liberty was started in the background with its own set of env's.

After stopping and starting the console inside a shell, which I did as part of my investigations, then the environment is no longer correct.

After re-starting the pod, I can now login to the console with TLS active.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant