BEA-090402 - Authentication Denied: Boot Identity Not Valid (Doc ID 740510.1)

Last updated on AUGUST 15, 2016

Applies to:

Oracle WebLogic Server - Version 9.2 and later
Information in this document applies to any platform.

***Checked for relevance on 15-Aug-2016***

Symptoms

After installing Oracle WebLogic Server 10.3 against Linux, then changing the password of the user account "system" (weblogic user) from "weblogic" to "manager", the server won't restart anymore, giving the error:

<Sep 30, 2008 12:51:29 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Sep 30, 2008 12:51:29 PM EDT> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
<Sep 30, 2008 12:51:29 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
>
<Sep 30, 2008 12:51:29 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Sep 30, 2008 12:51:29 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Sep 30, 2008 12:51:30 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Stopping PointBase server...
PointBase server stopped.

Changes

Changed the password of the user account "system" (weblogic user) from the default weblogic/weblogic to weblogic/manager.

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