|
Changing PeopleSoft Admin Passwords |
|
|
Written by Brent Martin
|
|
Thursday, 17 April 2008 |
|
One of the scariest things you can do is to change a password for one of your system accounts in a production environment. Your boss and users think it’s no big deal. Only you know how many places passwords need to be changed in the application. And if you don’t change each one and bounce the different components in the right order you’ll screw it up and look like a total idiot. Not that I’ve ever screwed it up. Primarily because I’m a consultant and changing passwords is nothing you want to pay a consultant to do. Yes, I like being a consultant. But I feel for all of you non-consultants out there, so I’ll list all of the places I’d change and you people who actually do change passwords let me know if I did it correctly or if I’d have some explaining to do:
PeopleSoft System Accounts: - 1) Change the password in psappsrv.cfg and psprcs.cfg. Just don’t reconfigure yet!
- 2) Change the password in integrationgateway.properties (don’t reload it yet!)
- 3) Change the password in your Signon PeopleCode (if you’re using Log On As)
- 4) Change the password in configuration.properties (PTWEBSERVER is probably the only ID here)
- 5) Change the password on the Web Profile (XMLLink, Public User, Custom Properties – AuditPWD)
- 6) Report Nodes if you’re using application accounts for authentication
- 7) Finally, change the password on the User Profile page.
- 8) Shut down the app servers, process schedulers and reconfigure. Shut down the Web server. Bring up the app servers and process schedulers. Bring up the web server.
PeopleSoft Network Accounts: - 1) If you’re using network passwords as part of your report repository configuration, go ahead and change the passwords to the new values.
- 2) Shut down PeopleSoft app server, web server, process scheduler, along with any PeopleSoft services running on Windows. Be sure to check all servers on the network.
- 3) Change the network password.
- 4) Change any Windows services that are using a network account. Generally the Tuxedo service and maybe the process scheduler services.
- 5) If you’re using Directory password authentication, change the password in your “Configure Directory” page
- 6) If you’re using a Single Sign On product like Gray Sparling’s SSO solution, you’ll need to change the network password(s) there.
- 7) Hopefully you’re not using system network accounts to map network drives, but if you do, disconnect and reconnect them.
- 8) Hopefully you don’t have passwords hard-coded in batch files to for interface purposes, but if you do change them now.
- 9) Verify the help desk is on speed dial and can unlock your account ASAP.
- 10) Start everything back up.
So how did I do?
Comments () |
 |
|
|
|
 |
