Reset the Admin Server password
How do I
reset the Admin Server's Administrator password?
Note: Please refer to Doc ID 1350814.1
1. Start the Admin Server and log-into console.
2. Go to page: Home > Summary of Security Realms > myrealm > Users and Groups > weblogic. and click on tab Passwords.
3. Enter the new Password.
4. Restart the server.
If you get a weblogic.security.SecurityInitializationException error, perform this additional step on every Managed Server (or eventually the Admin Server, too):
5. Go to folder DOMAIN_HOME/servers/AdminServer/security
6. Edit the boot.properties file and change the password to the value already entered on the Admin Console. Do this for all the servers in the domain.
7. Started the Admin Server (Weblogic Server will encrypt the password for you).
Optionally, you can force a Managed Server to connect to the embedded LDAP server on the Administration Server, instead of connecting to the local replicated LDAP server. Follow these steps:
8. Go to page: Domain > Security > Embedded LDAP page on the Admin Console
9. Enable MasterFirst.
10. Restart the server.
IF
YOU DON'T KNOW CURRENT PASSWORD
1.- Take the back of the LDAP folder of the admin server as well as managed server (you may rename those folders) and then delete the actual LDAP folder (found at servers\<MyServer>\data\ldap).
2. Make sure WebLogic instance is down.
3. Set your environment variables using setDomainEnv.sh.
4. cd to security directory in your instance.
(eg: $WL_HOME/user_projects/domains/base_domain/security)
5. Run:
java weblogic.security.utils.AdminAccount admin_user admin_pass .Remember to change “admin_user” and “admin_pass” to your need.
Also, don’t forget the period “.” at the end of the above command, it is required.
6. After running the command, the file “DefaultAuthenticatorInit.ldift” will get updated.
7. Delete the following file from “ldap” folder:
cd WL_HOME/user_projects/domains/base_domain/servers/AdminServer/data/ldap
rm DefaultAuthenticatormyrealmInit.initialized
8. Go to folder DOMAIN_HOME/servers/AdminServer/security
9. Edit the boot.properties file and change the password to the value already used on step 5. Do this for all the servers in the domain.
10. Start Weblogic Server (Weblogic Server will encrypt the password for you).
IMPORTANT
Keep in mind that we are NOT just changing the password for the Admin Console, but we are rather changing it for the Admin User (which may connect in many different ways to Admin Server).
Remember to use the new password (once successfully changed), when we try to connect to WLST or start the managed servers or even using weblogic.Admin utility.
1.- Take the back of the LDAP folder of the admin server as well as managed server (you may rename those folders) and then delete the actual LDAP folder (found at servers\<MyServer>\data\ldap).
2. Make sure WebLogic instance is down.
3. Set your environment variables using setDomainEnv.sh.
4. cd to security directory in your instance.
(eg: $WL_HOME/user_projects/domains/base_domain/security)
5. Run:
java weblogic.security.utils.AdminAccount admin_user admin_pass .Remember to change “admin_user” and “admin_pass” to your need.
Also, don’t forget the period “.” at the end of the above command, it is required.
6. After running the command, the file “DefaultAuthenticatorInit.ldift” will get updated.
7. Delete the following file from “ldap” folder:
cd WL_HOME/user_projects/domains/base_domain/servers/AdminServer/data/ldap
rm DefaultAuthenticatormyrealmInit.initialized
8. Go to folder DOMAIN_HOME/servers/AdminServer/security
9. Edit the boot.properties file and change the password to the value already used on step 5. Do this for all the servers in the domain.
10. Start Weblogic Server (Weblogic Server will encrypt the password for you).
IMPORTANT
Keep in mind that we are NOT just changing the password for the Admin Console, but we are rather changing it for the Admin User (which may connect in many different ways to Admin Server).
Remember to use the new password (once successfully changed), when we try to connect to WLST or start the managed servers or even using weblogic.Admin utility.
