After WLS Jul2016 CPU Patch or Upgrade of OID, DIP Sync to EBS Fails: <DIP-10013> <Exception java.security.AccessControlException: access denied ("oracle.security.jps.service.credstore.CredentialAccessPermission"
(Doc ID 2199808.1)
Last updated on AUGUST 30, 2023
Applies to:
Oracle Internet Directory - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
After applying Jul2016 CPU patch in WebLogic Server (WLS), Directory Integration Platform (DIP) is not provisioning / synchronizing user records to eBusiness Suite (EBS).
Applied Patch 23094342 , Patch 23623015, and Patch 22290164 per Jul2016 CPU in Oracle Internet Directory (OID) 11g 11.1.1.9.0.
The 10.3.6.0.160719 PSU Patch 23094342 in WLS is causing the following error in DIP logs:
<Oct 12, 2016 12:28:41 AM GMT+00:00> <Error> <oracle.dip> <DIP-10013> <Exception
java.security.AccessControlException: access denied ("oracle.security.jps.service.credstore.CredentialAccessPermission" "context=SYSTEM,mapName=dip,keyName=cn=odisrv" "read")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:395)
at java.security.AccessController.checkPermission(AccessController.java:559)
at oracle.security.jps.util.JpsAuth$AuthorizationMechanism$3.checkPermission(JpsAuth.java:478)
at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:538)
at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:564)
at oracle.security.jps.internal.credstore.util.CsfUtil.checkPermission(CsfUtil.java:691)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.getCredential(SspCredentialStore.java:608)
at oracle.ldap.odip.util.DirUtils$1.run(DirUtils.java:496)
at oracle.ldap.odip.util.DirUtils$1.run(DirUtils.java:494)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.ldap.odip.util.DirUtils.getCredential(DirUtils.java:493)
java.security.AccessControlException: access denied ("oracle.security.jps.service.credstore.CredentialAccessPermission" "context=SYSTEM,mapName=dip,keyName=cn=odisrv" "read")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:395)
at java.security.AccessController.checkPermission(AccessController.java:559)
at oracle.security.jps.util.JpsAuth$AuthorizationMechanism$3.checkPermission(JpsAuth.java:478)
at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:538)
at oracle.security.jps.util.JpsAuth.checkPermission(JpsAuth.java:564)
at oracle.security.jps.internal.credstore.util.CsfUtil.checkPermission(CsfUtil.java:691)
at oracle.security.jps.internal.credstore.ssp.SspCredentialStore.getCredential(SspCredentialStore.java:608)
at oracle.ldap.odip.util.DirUtils$1.run(DirUtils.java:496)
at oracle.ldap.odip.util.DirUtils$1.run(DirUtils.java:494)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.ldap.odip.util.DirUtils.getCredential(DirUtils.java:493)
NOTE: Same symptoms also found after upgrading OID from 11g to 12c.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |