Troubleshooting
Problem
Credentials Exception "org.omg.CORBA.NO_PERMISSION" when attempting to login to Workplace.
Symptom
When authentication via Workplace fails during logon, the following cause is shown in the detailed stack trace error:
Caused by: java.rmi.AccessException: CORBA NO_PERMISSION 0x49424300 No; nested exception is: org.omg.CORBA.NO_PERMISSION:
Trace log from CE server shows:
org.omg.CORBA.NO_PERMISSION: Subject is null. Authentication Failed. vmcid: 0x49424000 minor code: 300 completed: No
Note: this problem could also be applicable to Workplace XT
The authentication failure occurs with all users attempting to login to Workplace. However, logging in using FileNet Enterprise Manager is successful.
The following two conditions will occur if the LTPA key is the cause of the authentication failure:
1. All users attempting to log into Workplace get an “Invalid Credentials” error message. If so, examine the detailed stack trace of the error message.
2. If you identify the following error in the error stack, "java.rmi.AccessException: CORBA NO_PERMISSION 0x49424300 No; nested exception is: org.omg.CORBA.NO_PERMISSION", then verify that you can log into FileNet Enterprise Manager.
Cause
When the Content Engine and Application Engine run in different profiles of WebSphere, they need to have the LTPA key synchronized. If the key expires or is out-of-sync, you may encounter this type of credentials exception during logon.
Resolving The Problem
To correct the exception thrown during the authentication process follow these steps:
- Generate the LTPA key from the CE WebSphere profile
- Import this key into the Application Engine WebSphere profile
For step-by-step instructions, refer to the correct version of the FileNet P8 Platform Installation and Upgrade Guide corresponding to the version of P8 you are working with.
Was this topic helpful?
Document Information
Modified date:
20 April 2020
UID
swg21384165