Error "The run-as security principal <USERNAME> chosen for the EJB 'MobileBean(Application: nms-ws, EJBComponent: admin.jar)' is not a valid user principal in the current security realm" When Deploying nms-ws.ear (Doc ID 2706544.1)

Last updated on JUNE 05, 2024

Applies to:

Symptoms

On : 2.3.0.2.0 version, Installation

When attempting to deploy the nms-ws.ear, it fails with this error:

####<Jul 10, 2020 9:51:39,207 AM EDT> <Info> <EJB> <[MANAGED SERVER NAME]> <HOSTNAME> <[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <94164d6b-3218-4702-b59b-a7bf4af080cb-0000000b> <1594389099207> <[severity-value: 64] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-011061> <Stack trace associated with message Error occurred while setting up bean info to EJB:MobileBean follows: 

The run-as security principal, '<USER_NAME>', chosen for the EJB 'MobileBean(Application: nms-ws, EJBComponent: admin.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:844)
at weblogic.ejb.container.deployer.BeanInfoImpl.prepare(BeanInfoImpl.java:779)

The issue can be reproduced at will with the following steps:

1. Set the user name for the nms-ws.ear to a valid LDAP user.
2. Specify two authenticators.
3. Ensure the first authenticator cannot be contacted (i.e. it is not valid)
4. Set the Control Flag for the first authenticator to REQUIRED 
5. Set the Control Flag for the second authenticator to SUFFICIENT.
6. Attempt to deploy the nms-ws.ear file, it will fail.
7. Change the Control Flag for the first authenticator to SUFFICIENT
8. Attempt to deploy the nms-ws.ear file, it will succeed.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.