Discussion
Coforge
US
Last activity: 6 Apr 2018 19:26 EDT
"Problem accessing key store java.io.IOException: Invalid keystore format
Hi, We are upgrading from v5.5 to 7.1.9 ( Websphere / DB2-UDB). We completed upgrade, while validating upgrade we see none of the Connect-SOAP services are working. We are getting error in tracer as "keystore Exception: IBMKeyManager: Problem accessing key store java.io.IOException: Invalid keystore format"
in log we see error following errors. Any configuration we have to do after upgrade with respect to Connect-SOAP or it is expcetd to work without any change ? if changes required can someone guide me documentation around it please...
2016-01-07 10:18:39,695 [ WebContainer : 1] [TABTHREAD1] [ctCenterCPM:02.01.01] ( internal.ssl.SSLUtils) ERROR gicone-dev.prudential.com| Proprietary information hidden|Rule-Connect-SOAP.PruGI-Int-Insured-Insureds-.search2 x186475 - Unable to get environment's protocols java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: IBMJSSE2, class: com.ibm.jsse2.ec)
2016-01-07 10:18:39,708 [ WebContainer : 1] [TABTHREAD1] [ctCenterCPM:02.01.01] ( internal.ssl.SSLUtils) ERROR gicone-dev.prudential.com| Proprietary information hidden|Rule-Connect-SOAP.PruGI-Int-Insured-Insureds-.search2 x186475 - IBMKeyManager: Problem accessing key store java.io.IOException: Invalid keystore format
java.security.KeyStoreException: IBMKeyManager: Problem accessing key store java.io.IOException: Invalid keystore format
at com.ibm.jsse2.cc$a_.engineInit(cc$a_.java:7)
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
IN
Can you make sure that you are using same key store format in the WAS and Pega WS-Security Profile rule. Pega only supports jks store, the following article may be helpful.https://community.pega.com/support/support-articles/ws-security-cant-open-keystore
Coforge
US
Hi Dhevendra,
In 5.5 we are not sut any such keystors or ws-security profile... we have not configured services security at SOAP Connector level, it is configured at server level.
In such case after upgrade to 7.1.9, to make Connect-SOAP work in backward compatibility any steps we need to follow ?
Pegasystems Inc.
IN
AIG
US
In prior, we faced same issue and pega support has directed IBM issue. Please follow up with WAS administrator and go with quick fix-
Needs to convert the SSL cert to JKS and needs to upload at Truststore option of Keystore rule. And the Keystore rule needs to be mapped in WS Security profile rule and the same needs to be mapped at Connect SOAP rule. Refer https://community.pega.com/support/support-articles/ws-security-cant-open-keystore