OAM 11gR1/R2 : Unable to Access the /oamconsole After Installing WLS Performance Patch (Doc ID 1496503.1)

Last updated on SEPTEMBER 19, 2023

Applies to:

Symptoms

After following the OAM11gR2 installation steps , the OAM domain works as expected. After installing the WLS 10.3.6 Performance Patch (patch number : 13573621), when the WLS instances of the OAM domain are restarted, the Administrative user (default: weblogic) is no longer able to authenticate against the /oamconsole

In the AdminServer-diagnostic.log, the error below is reccorded :

[2012-10-05T14:28:10.919+02:00] [AdminServer] [ERROR] [OAM-69000] [oracle.oam.install] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000Jckt5YcFw005zz_AiW1GRh7Z000004,0] [APP: oam_admin#11.1.2.0.0] OAM configuration failed.[[
java.security.AccessControlException: access denied (oracle.security.jps.service.credstore.CredentialAccessPermission context=SYSTEM,mapName=OAM_STORE,keyName=jks write)
    at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
    at java.security.AccessController.checkPermission(AccessController.java:546)
    at oracle.security.jps.util.JpsAuth$AuthorizationMechanism$3.checkPermission(JpsAuth.java:458)
    at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:518)
    at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:544)
    at oracle.security.jps.internal.credstore.util.CsfUtil.checkPermission(CsfUtil.java:643)
    at oracle.security.jps.internal.credstore.ldap.LdapCredentialStore.setCredential(LdapCredentialStore.java:389)
    at oracle.security.am.install.OAMInstaller.configureKeyStore(OAMInstaller.java:337)
    at oracle.security.am.install.startup.OamInstallLifecycleListener.OamStartupOperations(OamInstallLifecycleListener.java:88)

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.