Getting Authentication Denied: Boot identity not valid while Starting Managed Server via Node Manager
(Doc ID 828298.1)
Last updated on DECEMBER 15, 2023
Applies to:
Oracle WebLogic Integration - Version 10.2 and laterOracle Service Bus - Version 10.3 and later
Information in this document applies to any platform.
Symptoms
When trying to start a Managed Server via Node Manager getting the following exception:
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 stacktraceWhen trying a start a Managed Server via Node Manager getting the following exception:
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |