My Oracle Support Banner

On Every Startup security/DefaultAuthenticatorInit.ldift Is Changed And Prevents Further Startup Of WebLogic Server (Doc ID 2363345.1)

Last updated on SEPTEMBER 10, 2018

Applies to:

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

Symptoms


On every startup the file security/DefaultAuthenticatorInit.ldift is changed and prevents further startup of WebLogic Server instance.

Some lines seen removed from DefaultAuthenticatorInit.ldift, this is confirmed by using diff command on security/DefaultAuthenticatorInit.ldift comparing with backed up file

> dn: uid=weblogic,ou=people,ou=@realm@,dc=@domain@
> description: weblogic
> objectclass: inetOrgPerson
> objectclass: organizationalPerson
> objectclass: person
> objectclass: top
> cn: weblogic
> sn: weblogic
> userpassword: {ssha256}dLY3OBi5Fc6f90MRYYy4O9YqoVaDpERL2wKXv8B9xKhRF6qt
> uid: weblogic
> objectclass: wlsUser
> wlsMemberOf: cn=Administrators,ou=groups,ou=@realm@,dc=@domain@


Server fails to start with following exception:

<BEA-090402> <Authentication denied: Boot identity not valid. The user name or password or both 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.>

 To successfully start the server security need to be recovered.

Changes

 

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
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.