Hi

We an application that checks the keystore for certificate. It is working in appserver1 but is encountering "Failed to load credentials" error in appserver2. Have tried to recreate the keystore and verified that the keystore password is correct. Hope somebody can help on this


08/11/2018 13:15:20:820 DEBUG - 8CD65B6C8AD99E55B85C63527E9D6CC1:/HORIZON_MEM_509 : Collecting [connectivity.ws.beans.service1.WebSvcSearchMember_v3Stub$Config@2dd3e5] from:pConfig
08/11/2018 13:15:20:820 INFO - 8CD65B6C8AD99E55B85C63527E9D6CC1:/HORIZON_MEM_509 : Signing soap message using keystore at C:\Program Files (x86)\Java\jdk1.7.0_05\jre\lib\security\cacerts.jks, alias: 1, provider: SUN, and a password with a length of 7
08/11/2018 13:15:21:133 ERROR - 8CD65B6C8AD99E55B85C63527E9D6CC1:/HORIZON_MEM_509 : Failed opening key store for signing soap message: Failed to load credentials.
08/11/2018 13:15:21:133 ERROR - 8CD65B6C8AD99E55B85C63527E9D6CC1:/HORIZON_MEM_509 : Failed signing envelope: Failed to load credentials.
08/11/2018 13:15:21:133 DEBUG - 8CD65B6C8AD99E55B85C63527E9D6CC1:/HORIZON_MEM_509 : session id:pdc-aep-mpp-2018312181423-17 | HORIZON_MEM_509:CallSearchMemberWS | WS Excetion while calling Search member WS for SSN

Are you sure you have a file named "cacerts.jks" exactly? Typical, Java does comes with a default truststore file but the name does not have "jks" extension. It's just "cacerts".

yes, cacerts.jks keystore was created . Speech application was coded to look for cacerts.jks.

Something is wrong with the truststore file then. Make sure it is jks format.

Have verified it is JKS format. We also tried to recreate it, same error is encountered. For the other application server, this is working. And we are using the same keystore location Java\jdk1.7.0_05\jre\lib\security\cacerts.jks

Have tried to copy the working keystore and same error.

It must be something in the environment. I can't really tell. The code would not complain about failing opening any jks even the one that does not have the certificate.