Change ConnectionsAdmin to be an LDAP user

For an existing installation of Connections with IBM FileNet , the connectionsAdmin user defined in the FileNet system must be available in the directory configuration of both FileNet and Connections. The easiest way to accomplish this may be to change to an LDAP user in a common directory

There are two ways to resolve this issue. You either can:

• Find a user in the LDAP directory that is accessible by both FileNet and Connections, and change the connectionsAdmin to be that user on both FileNet and Connections. Then update the DSX-Admin settings in Communities and update the SIB Bus information on Connections. To do so, follow these instructions:

  • Changing references to administrative credentials

  • Updating the messaging bus configuration when the connectionsAdmin user ID changes

• Add an existing LDAP user, and add this user to the Connections Admin to ensure that both Connections, and FileNet use that LDAP User. This method avoids having to change all the credentials and SIB Bus information. To add an existing user.

1. In Websphere Application Server WAS console on the FileNet server select Deployment Security > Global Security > Authentication: Java Authentication and Authorization Service > J2C authentication data .

   1. Change the connectionsAdmin user ID to the LDAP user name to use (instead of the WIM account name). Supply the credentials and then click Apply and OK.

   2. Restart FileNet server (server1).

2. In Websphere Application Server WAS console on the Connections deployment select Applications > WebSphere enterprise applications > Communities > Detail Properties: Security role to user/group mapping.

   1. Select the dsx-admin box and then click Map Users

   2. Enter the LDAP user's name in the Search string.

   3. Select this name from the Available box then click the arrow to add it to the Selected box.

   4. Click OK twice to save the master configuration and then restart Communities.

3. Prove the SSO connection still works.

   1. Open a browser session to FileNet, authenticate, and then in same browser window change the url to Communities. You should be logged in as the same user.

   2. Open a browser session to: <fileNetHostName>:<fileNetPort>/dm.

      The default HTTP port in FileNet is commonly set to 80 or 9080.

   3. Log in with the connectionsAdmin user you previously added.

   4. Change the url to: http://<connectionsHostName>/communities When the page loads you should be logged in as the same user you just logged in on FileNet. You should not be prompted for credentials.

Parent topic:
Configure the FileNet deployment used by Libraries