Manage stored credentialsIBM Connections does not create nor store user names and passwords. Instead, it uses the user credentials that already exist in your LDAP directory for authentication. IBM Connections does not store administrative user IDs and passwords either. It does, however, create and store references to existing administrative user credentials. You can make changes to those references.
User credentialsTo change a user's password, change the password in the LDAP directory that you are using to store user data. IBM Connections does not provide a method that administrators can use to change user credentials. Use the methods in place in your organization for changing user credentials. Alternatively, you can refer to the documentation provided with the LDAP directory that you are using.
Administrative credentialsWhen you install IBM Connections, it creates a set of references to the administrative user credentials it needs to access other tools and services to configure IBM Connections. Refer to the following topics for information on how to update these references.
Change the WAS administrative user ID password
Update the password for the administrative user ID used to configure IBM Connections on WAS.
Change references to database administrative credentials
Update the aliases that reference the administrative user IDs and passwords used to manage IBM Connections databases.
Change references to administrative credentials
Update the aliases that reference the administrative user IDs and passwords used to handle server-to-server communication.
Switching to unique administrator IDs for system level communication
When you install IBM Connections, you provide a user name and password for a system user account that is created by the installer to handle application-to-application communication. The installer also creates a J2C authentication alias, named connectionsAdmin. The alias is filled with the specified user and maps that user to a set of application roles. If you want to map these roles to different system user accounts, create additional J2C authentication aliases and remap the roles.
Update the messaging bus configuration when the connectionsAdmin user ID changes
If the connectionsAdmin alias is changed to use a different user ID than was previously configured, complete this procedure to ensure that applications can still communicate event information to the news service.
Change administrative credentials for the LDAP global unique ID
When you change the credentials of the administrative user ID that serves as the global unique ID for IBM Connections, also update the federated repository configuration for IBM Connections.
Change the password for the mail administrative user
If mail is configured to be sent from a dedicated mail server that requires authentication and update the credentials associated with it, you can change the password associated with mail.
Parent topicAdminister applications