==============================================================================
Applies To:
SOA Product Type: BPEL
- version 11.1.1.6.7
Oracle Database: Enterprise Edition - Version 11.2.0.3
==============================================================================
Admin Server is not able to start because of javax.security.auth.login.FailedLoginException:
[Security:090302]Authentication Failed: User weblogic denied
####<Mar 31, 2015 12:14:51 AM MYT> <Critical>
<WebLogicServer> <puru.com>
<poc_bpel_admin> <Main Thread> <<WLS Kernel>>
<> <> <1427732091824> <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(CommonSecurityServiceManagerDelegateImpl.java:960) at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054) at
weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at
weblogic.security.SecurityService.start(SecurityService.java:141)
at
weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at
weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at
weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: javax.security.auth.login.FailedLoginException:
[Security:090304]Authentication Failed: User weblogic
javax.security.auth.login.FailedLoginException: [Security:090302]Authentication
Failed: User weblogic denied at
weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261) at
com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110) At com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:597)
at
javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at
javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at
javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at
javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at
javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at
com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:597)
at
com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
at
$Proxy39.login(Unknown Source) at
weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89) at
com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:597) at
com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
at
$Proxy57.authenticate(Unknown Source) at
weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40) at
weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:338) at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:930)
at
weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at
weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
at
weblogic.security.SecurityService.start(SecurityService.java:141)
at
weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at
weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at
weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
####<Mar 31, 2015 12:14:51 AM MYT> <Error>
<WebLogicServer> <puru.com>
<poc_bpel_admin> <Main Thread> <<WLS Kernel>>
<> <> <1427732091887> <BEA-000383> <A critical
service failed. The server will shut itself down>
==============================================================================
Cause:
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.
===============================================================================
Solution:
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.
1.
Go to your AdminServer directory, $DOMAIN_HOME/servers/AdminServer
2.
Check the boot.properties file under security
folder and data/nodemanager folder if they have been changed recently.
3.
If file is been changed recently then restore it
from backup if you had taken it before change.
OR
If we don’t have backup for boot.properties file then we can follow below
process,
·
Take a backup of "data" folder, i.e.
just rename "data" directory to "data_bkp"
·
Inside AdminServer create a directory "security"
·
Inside the "security" directory create
a file with the name "boot.properties"
·
Edit boot.properties and enter the username and
password as shown below,
username=weblogic
password=weblogic1
·
Start webLogic server
No comments:
Post a Comment