OIF issue - Invalid/unsupported key store or incorrect password

When initiating the startup of the managed node, I would see the errors, oracle.security.fed.sec.key.select.KeystoreStore, cannot open the key store
October 7, 2015
OIFOAMkeystoresWeblogic

I would receive this error, "The server could not initialize properly: oracle.security.fed.sec.util.KeySourceException: Invalid/unsupported key store or incorrect password. Please verify that the password is correct and the store is a valid PKCS#12 PFX wallet or Java KeyStore file."

within the OIF 11gR1 logs when the federated nodes were initiated and requests were sent specifically to that weblogic node. This can be easily replicated if you try accessing the SP URL (http://HOSTNAME:7499/fed/sp/metadata).

Furthermore, when initiating the startup of the managed node, I would see the errors, oracle.security.fed.sec.key.select.KeystoreStore, cannot open the key store

https://technicalconfessions.com/images/postimages/postimages/_413_4_Confirming the JKS path for Oracle 11g products within WLS.png

This error is also non-OIF specific. I've blogged about keystore issues for OIM 11g and OAM 11g in the past. More often than not, if the error states that keystore cannot be 'opened' then it's indicative that the key store is located though could not be opened (perhaps because of a credential issue). The first thing to check is whether the .jks location within WLS can be located on the server

Comparing the location of the .jks within WLS console and running the following scripts such as ls -la /app/oracle/R1/middleware/wlserver_10.3/server/lib/DemoIdentity.jks and ls -la /app/oracle/R1/middleware/wlserver_10.3/server/lib/DemoTrust.jks to ensure they can be located if the first step

Once located, the next procedure is to validate the keystore. I always end up using this website for commands.
That said, I would often use the following command:
keytool -list -v -keystore /app/oracle/R1/middleware/wlserver_10.3/server/lib/DemoIdentity.jks -storepass DemoIdentityKeyStorePassPhrase
Obviously change the storepass of the JKS (the password used in the keytool query is the old default password Oracle used to use for creating the java keystore). If the command is executed correctly, you will see a few rows of text. One in mind is the 'Your keystore contains 1 entry', which basically means you're able to see the private certificates within the keystore. Knowing that the password is correct, go ahead and update the stored password within WLS.


When it's still not working

When I confirmed that there was nothing wrong with the keystore and that the error seemed to be misleading, I started to stew more towards the configuration setting issue than a JKS-specific issue. For OIF, it turned out that the configuration files needed to be transferred over once I created an additional node for high availability. This was achieved by moving the application config fils from one VM to my other local VM. This was executed by using using the following command:
scp -rp /app/oracle/middleware/user_projects/domains/base_domain/config/fmwconfig/servers/wls_oif1/applications/OIF_11.1.1.2.0 oracle@localhost.localdomain:/app/oracle/middleware/user_projects/domains/base_domain/config/fmwconfig/servers/wls_oif2/applications/
Once that was executed, the Cannot open the key store errors were no longer within the WLS log files and I was able to proceed with initiating the application from the node manager

About the author

Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles

Comments

Other Posts

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

ICFIDMOpenIDMOpenICF

November 8, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

org.forgerock.script.exception.ScriptCompilationException: missing ; before statement

IDMsync.confforgerockopenidm

November 8, 2017
Created by: Daniel Redfern
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen

OpenIDMsync.confForgeRock

September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups

OpenIDMForgeRockICFConnector

September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

OpenIDMForgeRockICFConnectorAD

September 17, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_g

OpenIDMIDMGoogleGoogle-AppsICFreconciliation

September 12, 2017
Created by: Daniel Redfern
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...

forgerock-openidm-encryptedjwt-error

OpenIDMIDMForgeRockJWTIAM

August 29, 2017
Created by: Daniel Redfern
Received the JWT error
Read More...

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...

OpenDJ Error - Connect Error Result Code: 91 (Connect Error)

OpenDJLDAPldapsearchForgeRock

June 5, 2017
Created by: Daniel Redfern
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
Read More...

Tomcat NioEndpoint$SocketProcessor.doRun java.lang.NullPointerException error

TomcatJava-8PKICAS

June 5, 2017
Created by: Daniel Redfern
When initiating the Tomcat instance, the cas-stderr log file will log a SEVERE error logging multiple times every few seconds
Read More...