Update user ID and passwords
WebSphere Portal and IBM WAS use some accounts from the registry (for example, the LDAP server) including administrative and bind IDs for authenticated access to databases and LDAP severs respectively, as well as the WebSphere Portal and WAS administrative IDs. Often this means that the account passwords are stored in the WebSphere Portal and WAS bootstraps configuration files, which allows the authentication process to work. Before updating any user ID or password, review "User IDs and passwords" located under Plan for WebSphere Portal.
If the password for any ID is changed (either through WebSphere Portal or through any other means, including directly through the LDAP administration interfaces), then the password value stored in the appropriate configuration file must be changed at the same time. The following instructions describe how to make the appropriate changes based on which account passwords might have changed.
If you reuse the same account ID/password for multiple purposes, such as using wpsbind as the administrative ID and the LDAP access ID, then you might have to do more than one of the following steps to accommodate the password change. Some changes, particularly changes made through the WAS console, require that the WAS console be open and the current ID/password logged in before actually making the password change in the registry. Carefully plan which steps are required and in what order to avoid not being able to bring up server processes or log in.
Use the following topics to change passwords to better secure environment.
- Change the WebSphere Portal administrator password
- Change the WAS administrator password in the file registry
- Change the WAS administrator password in the LDAP server using the LDAP administration interface
- Replace the WAS administrator user ID
- Replace the WebSphere Portal administrator user ID
- Change the LDAP bind password
- Change database passwords that are used by WebSphere Portal
Parent
Administering