OAM 11GR2 after install: OAM configuration failed access denied (oracle.security.jps.service.credstore.CredentialAccessPermission context=SYSTEM,mapName=OAM_STORE,keyName=jks write)

(Doc ID 1507922.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Access Manager - Version 11.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms

After installing OAM 11GR2 when starting for the first time the Admin Server the first error we get is :

[2012-11-01T11:59:42.264+00:00] [AdminServer] [ERROR] [OAM-69000] [oracle.oam.install] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 0000JevphLD2RP45zVt1iW1
G^aFj000004,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)

If we take a look at the OAM amtruststore and .oamkeystore are empty (0 bytes) which is normal as they are generated on the first start of the AdminServer

 

Taking a look at the install logs does not help as no error is reported and everything seems to have completed successfully as with the configureSecurityStore.py step

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms