OIM Server Starting in Admin State - "oiminternal" User not Found - is not a valid user principal in the current security realm. (Doc ID 2213623.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms



OIM server starting in Admin state - "oiminternal" User Not Found - Not valid user

"oim" application is showing Pending in Deployments page within WLS console.

AdminServer, SOA and OIM servers all having issues with invalid users.

ERROR
-----------------------
OIM server log shows:

<Error> <Deployer> <BEA-149205> <Failed to initialize the application 'oim [Version=11.1.2.0.0]' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(iam-ejb.jar)

Unable to deploy EJB: UnauthenticatedSelfService from iam-ejb.jar:

The run-as security principal, 'oiminternal', chosen for the EJB 'UnauthenticatedSelfService(Application: oim#11.1.2.0.0, EJBComponent: iam-ejb.jar)' is not a valid user principal in the current security realm. Please specify a valid user principal for the EJB to use.

.
weblogic.application.ModuleException: Exception preparing module: EJBModule(iam-ejb.jar)

Unable to deploy EJB: UnauthenticatedSelfService from iam-ejb.jar:

The run-as security principal, 'oiminternal', chosen for the EJB 'UnauthenticatedSelfService(Application: oim#11.1.2.0.0, EJBComponent: iam-ejb.jar)' is not a valid user principal in the current security realm. Please specify a valid user principal for the EJB to use.

at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
Truncated. see log file for complete stacktrace
Caused By: The run-as security principal, 'oiminternal', chosen for the EJB 'UnauthenticatedSelfService(Application: oim#11.1.2.0.0, EJBComponent: iam-ejb.jar)' is not a valid user principal in the current security realm. Please specify a valid user principal for the EJB to use.
at weblogic.ejb.container.deployer.BeanInfoImpl.calculateRunAsPrincipal(BeanInfoImpl.java:1025)
at weblogic.ejb.container.deployer.BeanInfoImpl.prepare(BeanInfoImpl.java:971)
at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.prepare(ClientDrivenBeanInfoImpl.java:992)
at weblogic.ejb.container.deployer.Ejb3SessionBeanInfoImpl.prepare(Ejb3SessionBeanInfoImpl.java:293)
at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:1031)
Truncated. see log file for complete stacktrace
.
.
<Error> <oracle.wsm.resources.policymanager> <WSM-02311> <Failed to retrieve requested documents due to underlying error "java.rmi.AccessException: [EJB:010160]Security Violation: User: 'OracleSystemUser' has insufficient permission to access EJB: type=<ejb>, application=wsm-pm, module=wsm-pmserver-wls.jar, ejb=DocumentManager, method=retrieveDocuments, methodInterface=Remote, signature={java.lang.String,java.util.Map}.".>
<Dec 12, 2016 11:27:17 AM CST> <Warning> <oracle.wsm.resources.policymanager> <WSM-02312> <Failed to store resource usage information to underlying error "java.rmi.AccessException: [EJB:010160]Security Violation: User: 'OracleSystemUser' has insufficient permission to access EJB: type=<ejb>, application=wsm-pm, module=wsm-pmserver-wls.jar, ejb=UsageTracker, method=recordUsage, methodInterface=Remote, signature={java.lang.String,java.util.Map,java.util.Set}.". The operation will be retried.>


AdminServer log shows:

<Warning> <oracle.wsm.resources.policymanager> <WSM-02310> <Failed to retrieve requested documents due to underlying error "java.rmi.AccessException: [EJB:010160]Security Violation: User: 'OracleSystemUser' has insufficient permission to access EJB: type=<ejb>, application=wsm-pm, module=wsm-pmserver-wls.jar, ejb=DocumentManager, method=retrieveDocuments, methodInterface=Remote, signature={java.lang.String,java.util.Map}.". The operation will be retried.>




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