When starting a java agent like the TLS Gateway agent the agent won't start and the following is shown in its log:
For each file in the trustedCertFolder, the following message:
java.security.cert.CertificateException: No certificate data found
Then:
U02000385 Web socket error: ‘sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target’.
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Caused by sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Caused by sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
U02000380 Could not connect to server ‘<IP>:<port>’.
U02000074 Connecting to system ‘<SYSTEM_NAME>’
com.uc4.ex.cp.InitialConnectionException: Initial connection with endpoint not possible. Please check your configuration
U02000041 Shutdown Agent ‘<AGENT_NAME>’.
U02000002 Agent ‘<AGENT_NAME>’ version ‘21.0.8+build.1692623685874’ ended abnormally.
Version: 21.0
The trustedCertFolder agent setting did not have the correct path to the certificate in it.
Doublecheck the trustedCertFolder= entry in the agent ini file that it points to folder with the certificate in it that corresponds to the JCP's keystore. For instance, if the certificate is in: C:\automic\agent\TLSGW\bin\cert
and the ini setting is:
trustedCertFolder=C:\automic\agent\TLSGW\bin
the agent will throw these errors.
In that example, the correct setting would be:
trustedCertFolder=C:\automic\agent\TLSGW\bin\cert