"Security violation: User DBA.ADMIN has insufficient permission to access EJB type" Exception Logging Into Newly Installed OTM (Doc ID 2103234.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Transportation Management - Version 6.4.0 to 6.4.2 [Release 6.4]
Information in this document applies to any platform.

Symptoms

When attempting to log into newly installed OTM 6.4.0 using DBA.ADMIN or GUEST.ADMIN, the following error occurs.

ERROR
-----------------------
INFO | 2015/12/23 12:20:37 | at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
INFO | 2015/12/23 12:20:37 | at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
INFO | 2015/12/23 12:20:37 | at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:523)
INFO | 2015/12/23 12:20:37 | at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
INFO | 2015/12/23 12:20:37 | at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
INFO | 2015/12/23 12:20:37 | at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
INFO | 2015/12/23 12:20:43 | java.rmi.AccessException: [EJB:010160]Security violation: User DBA.ADMIN has insufficient permission to access EJB type=, application=GC3App, module=UserAccessSession.jar, ejb=UserAccessSessionHome, method=getUserAccess, methodInterface=Remote, signature={java.lang.String,java.lang.String,java.lang.String,java.lang.String}.
INFO | 2015/12/23 12:20:43 | at weblogic.utils.StackTraceDisabled.unknownMethod()
INFO | 2015/12/23 12:21:25 | java.rmi.AccessException: [EJB:010160]Security violation: User GUEST.ADMIN has insufficient permission to access EJB type=, application=GC3App, module=UserAccessSession.jar, ejb=UserAccessSessionHome, method=getUserAccess, methodInterface=Remote, signature={java.lang.String,java.lang.String,java.lang.String,java.lang.String}.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Install OTM 6.4.0
2. Try to log in as GUEST.ADMIN or DBA.ADMIN
3. Get the error message mentioned above.


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