Changing the WebSphere Application Server administrator password in the LDAP server using the LDAP administration interface | HCL Digital Experience
If you are using the IBM Directory Server or IBM SecureWay Security Server for z/OS and OS/390 LDAP server, you can change the IBM WebSphere Application Server administrator password in the LDAP server using the LDAP administration interface. If you are using any other LDAP server, refer to the product documentation for information about changing passwords.
About this task
Procedure
- Log in to the LDAP server Web Administration Tool.
- Click .
- Select the o=wps RDN and click Expand.
- Select cn=users and click Expand.
-
Select the WebSphere®
Application Server administrator user and click Edit
Attributes.
Note: If this is your first time navigating to this screen, you may need to click Next before you can click the Optional attributes link.
- Click Optional attributes.
- Enter the new password in the userPassword field.
- Click OK.
- Exit the Web Administration Tool.
-
Complete the following steps to update the RunAsRole,
which changes the stored password:
You can change the password for the WebSphere® Application Server administrator user ID using the HCL Digital Experience Edit My Profile portlet, the native utilities for the user repository, such as the LDAP administration interface or the WebSphere® Application Server Administrative utilities. Regardless of which option you choose, once you have updated the password, you must also update the RunAsRole for the PZNScheduler application.
- Log on to the WebSphere® Integrated Solutions Console with your new password.
- Go to .
- Locate and click the pznscheduler application.
- Click User RunAs Roles under Detail Properties.
- Select RuleEventRunAsRole and then click Remove.
- Enter the fully distinguished name (DN) of the WebSphere® Application Server Administrator in the username field and the new password in the password field.
- Select RuleEventRunAsRole and then click Apply to apply your changes.
- Click OK, save your changes, and then restart the server.