Last updated on APRIL 07, 2017
Applies to:Business Intelligence Suite Enterprise Edition - Version 18.104.22.168.1 to 22.214.171.124.5 [Release 11g]
Information in this document applies to any platform.
Customer has a business requirement to have two different Admin Users to start weblogic in their OBIEE environment.
Customer created two admin users "biadmin" and "obiadmin" which have admin access to OBIEE system and have the same groups assigned.
Both biadmin and obiadmin can login to weblogic console and em.
We usually start the OBIEE system (weblogic, BIserver, OPMN) using the 'biadmin".
It was observed, the Weblogic server is unable to start when "obiadmin" user is used.
Due to security constraints, Customer do not want to have any boot.properties files for both Weblogic and BIserver at below locations
Weblogic server is started using the below command which has user id and password.
nohup ./startWebLogic.sh -Dweblogic.management.username=biadmin -Dweblogic.management.password=***** >nohup.out 2>&1 &
However when the new weblogic user OBIADMIN was used, nohup command failed and following error was seen in the nohup.out
<Security initializing using security realm myrealm.>
<Authentication for user obiadmin denied>
<Mar 7, 2017 10:33:07 AM EST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user obiadmin denied
weblogic.security.SecurityInitializationException: Authentication for user obiadmin denied
However the new user and the new password worked without any issue in the interactive mode and also with boot.properties file.
The issue was tested internally and error was reproduced.
When the obiadmin user was created password containing special characters were used
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms