This site is currently read-only as we are migrating to Oracle Forums for an improved community experience. You will not be able to initiate activity until January 31st, when you will be able to use this site as normal.

    Forum Stats

  • 3,890,647 Users
  • 2,269,776 Discussions


Weblogic 10.3.6 Admin server authentication issue

987959 Member Posts: 3
edited Jun 9, 2015 5:38PM in WebLogic Portal

We are getting below exception while starting the admin server

<Jun 1, 2015 9:58:23 AM UTC> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>

<Jun 1, 2015 9:58:23 AM UTC> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file ( 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.>

have tried below options but no luck.Appreciate quick help

1) Backup the WLS Domain

2) Rename/Delete $DOMAIN_DIR\security\DefaultAuthenticatorInit.ldift

3) Run the Java command:

          java <new-admin-user-name> <new-admin-user-pwd> <$DOMAIN_DIR\security>

4) Delete the contents inside the file [] under $DOMAIN_DIR\servers\<admin-server-name>\security.

5) Add the folllowing contents.



6) Delete the folder: $DOMAIN_DIR\servers\<admin-server-name>\data\ldap

7) Restart the WLS server


  • User10656774-Oracle
    User10656774-Oracle Member Posts: 52 Employee
    edited Jun 1, 2015 9:19AM


    is it w Abelogic Server or WebLogic Portal domain ?

  • 987959
    987959 Member Posts: 3
    edited Jun 4, 2015 7:17AM


    Its Weblogic server

  • Kevin Hooke
    Kevin Hooke Member Posts: 16
    edited Jun 8, 2015 1:44PM

    We started seeing the same issue with Weblogic Portal 10.3.6 domains created on developer machines - the issue started occurring on Friday last week 6/5/15 (not sure if this date is significant?). Issue started occurring on multiple developer machines. The only workaround we've found so far is to reinstall WLP. Even creating a new domain on the existing install does not fix the issue.

    Did something break that is date/time sensitive regarding encryption of this file?

  • Amit Brahmbhatt, 3Di
    Amit Brahmbhatt, 3Di Member Posts: 22 Blue Ribbon
    edited Jun 9, 2015 5:38PM

    Remove the file and start the weblogic server using the command line You will be prompted for the username and password. Enter the username and password that you think is correct and see if weblogic server starts.

    If it starts, then shutdown the WebLogic Server and then create the file with the username and password and then start the server again and see what happens.



This discussion has been closed.