How single sign-on works
Connections uses single sign-on (SSO) to secure the transfer of user ID and password information that is used to authenticate with the system. With SSO, users can switch to different applications without needing to authenticate again.
SSO is automatically enabled when IBM
Connections is installed on a single WebSphere
® Application Server profile or when different profiles are federated into the same cell.
SSO solutions can inadvertently block back-end server-to-server communication. IBM
Connections uses a server-to-server authenticator to prevent internal communication being blocked by your SSO solution. The configuration settings for the authenticator are stored in the customAuthenticator element in the LotusConnections-config.xml
Parent topic: Security
Setting up federated repositories
Configuring IBM Connections for SSO