Boot WLS 9.1 Administrative Console

Question

Hello everybody,
Glad to see I'm still marked as a Greenhorn. Someone in our group lost a memory stick loaded with our passwords and so we are going through changing them.
After changing a WebLogic 9.1 Administrtive Server password for Admin user X I decided to add a new user Y with the <default properties>, same as user X and then delete user X.
This didn't work as you could have guessed, seems i left a step out somewhere. Now user X doesn't exist and so I can't boot the Administrative Server as user Y doesn't have the rights.
On my attempts to do so I get this BEA system error message:
<BEA-090404>
Critical: User userName is not permitted to boot the server; The server policy may have changed in such a way that the user is no longer able to boot the server.Reboot the server with the administrative user account or contact the system administrator to update the server policy definitions.
Description
     The user userName has not been granted the necessary permission to boot the server.
Cause
     The server policy may have changed in such a way that the user is no longer able to boot the server.
Action
     Reboot the server from the administrative user account or contact the system administrator to update the server policy definitions.
Question: How do I edit these 'server policy definitions' without an admin server console or even an admin server running? (e.g. vi)
Thanks very much.

Answer 1

Note: ii. rm -rf ldap (it will be recreated by WLS on startup
Just to be clear (for people who just skim your note ). It will only be
recreated on managed servers (downloaded from admin server) so don't do this
on the admin server.
<John Grogan> wrote in message news:[email protected]...
OK, here is what I had to ultimately do that fix my problem:
How to changed Administrative Users for BEA WLS 9.0:
01. Stop the WLS 9 admin server
02. Stop all the nodemanagers/applications servers (on same or other machs)
03. Run a restore (from tape or whatever) on each mach for the affected
domain to a date before user security got messed up
04. On the nodemanagers/applications servers for the affected domain
i. cd <BEA WLS INSTALL DIR>/<DOMAIN DIR>/<APP SERVER DIR>/data
ii. rm -rf ldap (it will be recreated by WLS on startup
05. Start Admin Server & each Application Server
06. Log into Admin Console
07. Lock & Edit (may not strictly be needed, not sure)
08. Nav to Security Realms/myrealm/Users & Groups
09. New User add
10. Save
11. Nav to Groups -> add the New User I added to Administrators group
11. Save
12. Nav to Password & set password for New User
13. Save
14. Release Configuration (if Lock & Edit was done)
15. Stop each of the Admin Server & Application Servers
16. For each boot.properties for the Admin Server & Application Servers,
edit them to have username= / password= to reflect to new user / password
you just created (in clear text, the entries will be again encrypted by WLS
on startup)
17. For each Application Server only, again delete the ldap directory (may
not strictly be needed but these will be recreated on start up)
18. Start the Admin Server & Application Servers.
19. Log into Admin Console to verify.
20. Now delete the old Administrative User
21. Lock & Edit
22. Nav to Security Realms, myrealms, User & Groups.
23. Check the box by the old Administrative User & select Delete.
24. (Save?) can't remember but it would but hightlighted.
25. Release Configuration.
26. Stop the Administrative Servers & each Application Server
27. Start the Application Server & each Application Server
28. Done
I included extra steps to ensure access to the configuration throughout.