Use the following procedure to:
Change the repository password
Update the application to use the modified repository information
It is recommended that you perform each of these steps in the order presented. If you change the repository password at a time other than when directed in this sequence, problems can occur.
If Identity Manager connects to the repository with a JDBC driver, or if it connects to the repository using a Data Source that does not contain the connection user name and password, then use the following procedure to change the user or password:
The examples used in this procedure are for a MySQL repository. Some steps may vary depending on the specific repository used.
If you have deployed Identity Manager in an application server cluster, you should operate on the main source folder for Identity Manager (from which the application server deploys the IDM web application), rather than on each target folder (to which the application server deploys the web application on a particular server or node within the cluster).
Shut down Identity Manager. If you have deployed Identity Manager in a cluster, then you must stop all instances of the web application across the cluster.
Verify the existing repository:
Identity Manager responds with the current repository information; for example:
Create a temporary file system repository location:
Set Identity Manager to use the temporary file system repository location:
lh setRepo -tLocalFiles -fc:\tempfs LocalFiles:c:\tempfs
Change the password for your repository. This procedure depends on the mechanism provided by your repository provider. This example highlights steps for a MySQL database:
mysqladmin.exe -hlocalhost -uwaveset -poldpasswd password newpasswd
Set the application to use the modified repository information:
lh setRepo -tMysql -ujdbc:mysql://localhost/waveset -Uwaveset -Pnewpasswd
The application responds with this warning:
WARNING: No UserUIConfig object in repository. MysqlDataStore:jdbc:mysql://localhost/waveset
The warning message appears because the temporary file system that you pointed to has no contents. Ignore this message; after running the command, the temporary file system will no longer be needed.
Verify the new repository value:
lh setRepo -c
The application responds with the new value:
Restart the server and verify that you can log in. If you have deployed Identity Manager in a cluster, then you must re-deploy Identity Manager across the cluster. This will distribute the updated web application (which includes the updated ServerRepository.xml file), to all nodes in the application server cluster.
Remove the c:\tempfs temporary directory, and the ServerRepository.xml file that you archived in Changing a Repository Password Stored in a Database.