Since Weblogic stores it’s primary admin user account “weblogic” encrypted on disc, simply changing this users password in the console is not all there is.
Basic step: changing the password:
- Go to: Security Realm -> myrealm > Users and Groups >weblogic -> Passwords
- Change the password of the user, as you would normally do for every user
Stopping all managed servers
During step 3 we will change the NodeManager password. After this step the Admin console can no longer communicatie with the NodeManager so stopping/starting instances will not succeed.
Changing the Nodemanager password in the Weblogic Console:
- Use the Weblogic /console
- Go to Domain -> General -> Security -> Advanced
- Change the value for the Nodemanager Password
Attention!!!: The next steps will be necessary on each physical server of the domain:
Changing the Nodemanager password:
If you start/stop the Managed Servers through the NodeManager you will need to edit the so called nm_properties file
- Navigate your Linux/Windows file system and go to: %domain_home%/config/nodemanager
- Open nm_properties
- The file will hold encrypted values, replace all content with:
username=weblogic
password=myNewPassword01
- Restart the NodeManager
- Check nm_properties file for encrypted values
#Node manager user information
hashed=Y+kAE14jdmGFtI/wXxNRIoo0Jsb\=
Changing the Weblogic security file
If you decided to not use the NodeManager for start/stop Managed Servers but use the Weblogic start/stop scripts you will probably have your good reasons and you will need to edit the so called boot.properties file
- Navigate your Linux/Windows file system and go to: %domain_home%/servers/myserver01/security
- Open the boot.properties file
- Change the values to
username=weblogic
password=myNewPassword01
Launching the ManagedServer through the Startscript will test the result and encrypt the content.
Example: %domain%\bin\startManagedWeblogic rbx_dev_wls01 http://server01:7001
Sam
16-06-2012 at 05:45
very useful info…thank you
Grace
28-08-2012 at 17:36
This is very helpful. I am trying to change the admin password for my OSB domain. I have seen another post somewhere online that says simply updating the admin server boot.properties file then restarting the admin server and all the managed servers in the domain. Would that achieve the same purpose? I am somewhat new to OSB and is trying to understand the difference in updating the password in the console vs. in the boot.properties file. Any help would be appreciated.
Thanks,
Grace
jvzoggel
29-08-2012 at 08:22
hello Grace. The boot.properties or nm_properties are used to start the managed server and make sure they can connect to the admin & domain. I think you should need to change the password in Weblogic itself to make sure both are in sync. I never tried the “only-admin” boot.properties modification, but if you tested it and it works please let me know.
Isha
30-01-2014 at 23:41
Excellent article.
Helps a lot!
Thank You!
One Correction though :-
Under step :-
Changing the Nodemanager password:
If you start/stop the Managed Servers through the NodeManager you will need to edit the so called nm_properties file
Navigate your Linux/Windows file system and go to: %domain_home%/config/nodemanager
Open nm_properties
There is a typo here.
Please change nm_properties to nm_password.properties.
Just so that new bees like me don’t get confused.
AB
10-09-2015 at 16:51
Hi,
Weblogic server version – 10.3.6.
Executed the above steps.But after this change the user is getting locked out.
Getting message –
But the server is starting up without any issues.Kept the node manager server down and tried the same.Still the issue exist.
Any pointers will be appreciated.
AB
10-09-2015 at 16:52
Pasting logs for above issue.
Ban Ăn Chơi
30-11-2016 at 11:19
Thanks, nice explanation
RM
10-04-2019 at 18:03
Hi, I have followed the steps but ess_server 2 and soa_server2 won’t start. Am I missing something?
RM
11-04-2019 at 16:34
Hi, finally worked. Followed >> https://community.oracle.com/message/14595101#14595101