You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When enabled TLS for MQ and enabled DOA, the Java application fails with the following error:
TLS connection failed: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
If the MQ server TLS verification is enabled and both the MQ's cert and DOA's cert are signed by self-signed CA certificate of the used Issuer (not publicaly trusted), the verification fails.
After examining, I found that the keystore set by the init container might not be used. I tried adding the following lines to the doa-deply.yaml:
...to override the java -jar /localega-doa.jar built into the image. The TLS verification of the MQ server works now, but verification of client (DOA) still not.
Describe the bug
When enabled TLS for MQ and enabled DOA, the Java application fails with the following error:
If the MQ server TLS verification is enabled and both the MQ's cert and DOA's cert are signed by self-signed CA certificate of the used Issuer (not publicaly trusted), the verification fails.
After examining, I found that the keystore set by the init container might not be used. I tried adding the following lines to the
doa-deply.yaml
:...to override the
java -jar /localega-doa.jar
built into the image. The TLS verification of the MQ server works now, but verification of client (DOA) still not.Steps to reproduce
MQ (sda-mq) configuration:
DOA (sda-svc) configuration:
Expected behavior
Additional context
Full log:
Estimation of size: small
Estimation of priority: medium
The text was updated successfully, but these errors were encountered: