Customizing login attributes
Customizing the login attributes for IBM Connections is broken into two parts:
Configuring WebSphere Application Server Security
- Configuring WebSphere Application Server (WAS) security to allow login
- Configuring Connections to map the logged in WAS user to an entry in the Connections Profiles database
Configuring WebSphere Application Server Security and login is described in the WebSphere Application Server product documentation:
It is a useful diagnostic process to prove that you can log in to WAS regardless of the Connections configuration, and this can usually be achieved by starting the default WebSphere Application Server server1
and hitting the snoop servlet. The snoop servlet is typically installed as part of the DefaultApplication and is typically accessible on port 9080. E.g. http://testsrv01.demos.ibm.com:9080/snoop
It is not possible to Customize login attributes for Connections until you can login to WAS with those attributes.
Customizing Connections login attributes
Within the profiles-config.xml
file, the following section defines the fields that Connections will use to map a logged in WebSphere Application Server user to the Profiles database.
It is the 3rd attribute loginId that allows a custom value. (loginId refers to the Prof_Login column of the Employee table in the Profiles database)
When mapping LDAP attributes to the Profiles database during the Install process, your chosen custom login attribute should be mapped to the loginId attribute in Profiles.
The result is that when you login to WebSphere Application Server with your chosen attribute, the attribute is looked up in the Prof_login column of the Employee Table in the profiles database.
Parent topic: 5.0 Customizing Profiles