weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.

Tony007

hi am geting this error when starting weblogic am in solaris spack t4 with weblogic 12c form

forms its not sking for prompt to enter weblogic passwor but i have deleted boot.properties

Forms [64 Bit] Version 12.2.1.4.0 (Production)

Oracle Toolkit Version 12.2.1.4.0 (Production)

PL/SQL Version 12.1.0.2.0 (Production)

Oracle Procedure Builder V12.2.1.4.0 - Production

PL/SQL Editor (c) WinMain Software (www.winmain.com), v1.0 (Production)

Oracle Query Builder 12.2.1.4.0 - Prod

403> <Authentication for user weblogic denied.>

<Jun 7, 2021 11:33:43,149 AM SAST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: A MultiException has 4 exceptions. They are:

1. weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.

2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.security.SecurityService

3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.nodemanager.adminserver.NodeManagerMonitorService errors were found

4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.nodemanager.adminserver.NodeManagerMonitorService

A MultiException has 4 exceptions. They are:

1. weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.

2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.security.SecurityService

3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.nodemanager.adminserver.NodeManagerMonitorService errors were found

4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.nodemanager.adminserver.NodeManagerMonitorService

    at org.jvnet.hk2.internal.Collector.throwIfErrors(Collector.java:89)

    at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:250)

    at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:358)

    at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)

    at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:305)

    Truncated. see log file for complete stacktrace

Caused By: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.

    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:1158)

    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.postInitialize(CommonSecurityServiceManagerDelegateImpl.java:1272)

    at weblogic.security.service.SecurityServiceManager.postInitialize(SecurityServiceManager.java:586)

    at weblogic.security.SecurityService.start(SecurityService.java:130)

    at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:76)

    Truncated. see log file for complete stacktrace

Caused By: javax.security.auth.login.FailedLoginException: [Security:090938]Authentication failure: The specified user failed to log in. javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User specified user denied

    at com.bea.common.security.utils.ExceptionHandler.throwFailedLoginException(ExceptionHandler.java:62)

    at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:381)

    at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:117)

    at java.security.AccessController.doPrivileged(Native Method)

    at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:114)

    Truncated. see log file for complete stacktrace

>

<Jun 7, 2021 11:33:43,167 AM SAST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>

<Jun 7, 2021 11:33:43,167 AM SAST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>

<Jun 7, 2021 11:33:43,170 AM SAST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>

Stopping Derby server...

Derby server stopped.

-bash-5.0$

i try this am in 12c

https://stackoverflow.com/questions/12975671/how-restart-weblogic-server-after-authentication-error

https://www.technicalconfessions.com/posts/Issue-Authentication-for-user-weblogic-denied

Michael Ferrante-Oracle

It sounds like you may have corrupted the environment. However, before suggesting you recreate the domain consider this:

.1. You said, you "deleted boot.properties". Which one? If you were using this functionality, likely you would have one for each server (e.g. Admin Server, WLS_FORMS, WLS_REPORTS, etc). Which did you delete and which server are you trying to start?

.2. Why not put the boot.properties back in place, but with the correct information? It's easy to create the file. Simply do the following and the values will become encrypted the first time the servers are started.

In the file add the following two lines (replace values with your correct values):

o Ensure that ALL servers are not running.

o Create an empty text file and save it as boot.properties

username:MYUSERNAME

password:MYPASSWORD

o Save the file in each of the desired server's "security" directory. For example:

$DOMAIN_HOME/servers/AdminServer/security

If the "security" sub-directory does not exist, create one.

Tony007

i delete the boot.properties in Admin Server, WLS_FORMS, WLS_REPORTS it was with correct password i what to start admin server it does not ask for prompt to enter weblogic user/password but boot.properties is deleted

Tony007

i also re create domain still geting same error

Michael Ferrante-Oracle

Things to consider:

1 The middle tier must have access to the repository database at all times. You cannot shut down the DB and expect the middle tier to work as expected.

2 The mid tier servers should be started in this order, one at a time: Node Manager, Admin Server, then managed servers (WLS_FORMS, WLS_REPORTS, etc).

3 By default, DB passwords expire after a period of time. This means that WLS Repository schema passwords will have to be reset periodically. If you allow them to expire the middle tier servers will not have access and therefore will not start.

4 Passwords are case sensitive, so WELCOME1 is not the same as Welcome1