Home
Configure the custom ID attribute for users or groups
Configure Lotus Connections to use custom ID attributes to identify users and groups in the LDAP directory.
Ensure that you have completed the steps to specify different ID attributes for users and groups in the Specifying a custom ID for users or groups topic. If you specified a single ID attribute for both users and groups, you don't need to complete this task.
By default, Lotus Connections looks for LDAP attributes to use as the global unique IDs to identify users and groups in the LDAP You can change the default setting to use a custom ID to identify users and groups in the To configure Lotus Connections to use the custom ID attribute that you specified earlier...
- Add the new attribute to the LotusConnections-config.xml file. To do so...
- Start the wsadmin tool.
- Access the Lotus Connections configuration file:
- Stand-alone deployment
execfile("connectionsConfig.py")- Network deployment
execfile("WAS_HOME/profiles/Dmgr01/config/bin_lc_admin/ connectionsConfig.py")
If you are prompted to specify which server to connect to, type 1. This information is not used by wsadmin when you are making configuration changes.
- Check out the Lotus Connections configuration files...
LCConfigService.checkOutConfig("/<working_directory>", "cell_name")where
- /<working_directory> is the temporary working directory to which the configuration XML and XSD files are copied. The files are kept in this working while you change them.
- cell_name is the name of the IBM WebSphere Application Server cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. This argument is also case sensitive. If you do not know the cell name, do one of the following to determine it:
- Stand-alone deployment: Look at the name in the following directory in the file system: WAS_HOME\profiles\profile_name\config\cells\
- Network deployment: From wsadmin...
print AdminControl.getCell()
For example:
LCConfigService.checkOutConfig("/temp","foo01Cell01")
- From the temporary to which you checked out the Lotus Connections configuration files, open the LotusConnections-config.xml file in a text editor.
- Add the new custom properties to the LotusConnections-config.xml file. For example:
<sloc:serviceReference serviceName="directory" communities.directory.service.extension.auth="DSX-Admin" communities.directory.service.extension.auth.alias="connectionsAdmin" communities.directory.service.extension.enabled="true" communities.directory.service.extension.href= "http://enterprise.example.com:9080/communities/dsx/" profiles.directory.service.extension.auth="None" profiles.directory.service.extension.auth.alias="connectionsAdmin" profiles.directory.service.extension.enabled="true" profiles.directory.service.extension.href= "http://enterprise.example.com:9080/profiles/dsx/" custom_user_id_attribute="customUserID" custom_group_id_attribute="customGroupID"/>
- Save the LotusConnections-config.xml file.
- Check in the changed configuration property files...
LCConfigService.checkInConfig()
- (Network deployment only.) After making updates, enter the following command to deploy the changes:
synchAllNodes()
- Stop and restart the WebSphere Application Server instance hosting Lotus Connections.
Related tasks
Specify a custom ID attribute for users or groups