Users created in the WebLogic Console throw exception, "java.lang.SecurityException" when accessing composite components in the EM Console
(Doc ID 2016699.1)
Last updated on MAY 02, 2023
Applies to:
Oracle SOA Suite - Version 11.1.1.6.0 and laterInformation in this document applies to any platform.
Symptoms
On : 11.1.1.6.0 version, BPEL Service Engine
When new users are created in the WebLogic Console with the Monitor or Admin role, they are able to login into EM Console but while accessing SOA Infra components, the below exception is thrown:
oracle.sysman.emSDK.app.exception.EMSystemException
at oracle.sysman.emai.model.sca.WLSObjectHelper.createLocator(WLSObjectHelper.java:71)
at oracle.sysman.emai.model.sca.SCAObjectHelper.getLocator(SCAObjectHelper.java:92)
at oracle.sysman.emai.model.sca.SCAObject.getLocator(SCAObject.java:84)
at oracle.sysman.emai.model.sca.share.SCASharedModel.getLocator(SCASharedModel.java:21)
at oracle.sysman.emai.model.sca.share.composite.CompositeInstances.rangeChanged(CompositeInstances.java:222)
at oracle.sysman.emai.model.sca.share.common.SCADataModel._fetchBlock(SCADataModel.java:173)
at oracle.sysman.emai.model.sca.share.common.SCADataModel.setRowIndex(SCADataModel.java:130)
Caused by: java.lang.SecurityException: User: testuser, failed to be authenticated.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServiceImpl.java:116)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
... 2 more
at oracle.sysman.emai.model.sca.WLSObjectHelper.createLocator(WLSObjectHelper.java:71)
at oracle.sysman.emai.model.sca.SCAObjectHelper.getLocator(SCAObjectHelper.java:92)
at oracle.sysman.emai.model.sca.SCAObject.getLocator(SCAObject.java:84)
at oracle.sysman.emai.model.sca.share.SCASharedModel.getLocator(SCASharedModel.java:21)
at oracle.sysman.emai.model.sca.share.composite.CompositeInstances.rangeChanged(CompositeInstances.java:222)
at oracle.sysman.emai.model.sca.share.common.SCADataModel._fetchBlock(SCADataModel.java:173)
at oracle.sysman.emai.model.sca.share.common.SCADataModel.setRowIndex(SCADataModel.java:130)
Caused by: java.lang.SecurityException: User: testuser, failed to be authenticated.
at weblogic.common.internal.RMIBootServiceImpl.authenticate(RMIBootServiceImpl.java:116)
at weblogic.common.internal.RMIBootServiceImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:667)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:522)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:518)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
... 2 more
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 |