09 August 2016

weblogic.security.SecurityInitializationException: Authentication for user weblogic denied

This is a common exception that is under authentication scope.
Googling you can find a lot of information related to boot.properties and ldap directory.

Nevertheless, this time is about the Managed Server cannot communicate with Admin Server, thus it starts in independent mode, but being the very first time it doesn't have users from realms, finally any user cannot authenticate to MS.

Well, solving the name MBP.local (in my case), everything is solved. (etc/hosts :P )



<Aug 8, 2016 9:13:58 AM EDT> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://MBP.local:7001.>
<Aug 8, 2016 9:13:58 AM EDT> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>

....

.....
....

<Aug 8, 2016 9:13:59 AM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Aug 8, 2016 9:13:59 AM EDT> <Critical> <Security> <BEA-090403> <Authentication for user weblogic denied>
<Aug 8, 2016 9:13:59 AM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
  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)
  Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Authentication Failed: User weblogic weblogic.security.providers.authentication.LDAPAtnDelegateException: [Security:090295]caught unexpected exception
  at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:251)
  at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
  at java.security.AccessController.doPrivileged(Native Method)
  at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  Truncated. see log file for complete stacktrace
>
<Aug 8, 2016 9:13:59 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Aug 8, 2016 9:13:59 AM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>




No comments :

My Blog List

Blog Archive

There was an error in this gadget

Disclaimer

The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.