Identity Management (MOSC)

MOSC Banner

OAM 11.1.2.3 to 12.2.1.3 upgrade not working.

edited Aug 23, 2020 5:04AM in Identity Management (MOSC) 6 commentsAnswered

Has anyone upgraded OAM 11.1.2.3 to 12.2.1.3 successfully?  Do you need to have UserIdentityStore1 as SystemStore prior to upgrade?  We have MigratedStore as System/User Store.

The upgrade assistant went fine with no issues.  However, the upgrade did not create $DOMAIN_HOME/output/ss-webgate-SHA-256 directory.

Admin Server starts up fine but I am seeing weird errors in oam_server1 logs. 

<Jun 26, 2020 6:05:02,925 PM EDT> <Error> <oracle.oam.proxy.oam> <BEA-000000> <Exception in reading the SSL configuration

java.lang.IllegalArgumentException: Null input to method

        at oracle.security.am.common.utilities.crypto.CryptoUtil.hexToRaw(CryptoUtil.java:88)

        at oracle.security.am.common.utilities.crypto.OAMKeyStore.decryptSensitiveData(OAMKeyStore.java:252)

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center