+

Search Tips   |   Advanced Search

Change references to administrative credentials

Update the aliases that reference the administrative user IDs and passwords used to handle server-to-server communication.

This task is optional.

  1. To update the aliases that manage server-to-server communication, edit the associated J2C authentication data for the alias. In the WAS administration console, select... '

      Security | Global security | Authentication | Java Authentication and Authorization Service | J2C authentication data | connectionsAdmin

    You defined the current user ID and password to use for the connectionsAdmin alias during the installation. The user ID and password must be one of the following values:

    • A valid user in the organization's LDAP service. Organizational security requirements might require you to change this password periodically, in which case the stored credentials must be updated to reflect the new password.

    • A user defined in the WebSphere Identity Manager.

  2. Update the values that changed.

  3. Apply and save the changes.

  4. Restart the servers that host IBM Connections.

  5. If we changed the administrative user, update the mappings for the admin, dsx-admin, search-admin, trustedExternalApplication, and widget-admin Java EE roles. See Switch to unique administrator IDs for system level communication.

  6. Perform some additional steps to update the messaging bus configuration, which also relies on the connectionsAdmin alias. See Updating the messaging bus configuration when the connectionsAdmin user ID changes for more details.


Parent topic:
Manage stored credentials


Related:

Configure J2C authentication for Search

Update the messaging bus configuration when the connectionsAdmin user ID changes

Switch to unique administrator IDs for system level communication

Enable single sign-on for SiteMinder with SPNEGO