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.
Configuring basic authentication allows the manual entry of user credentials in the personalize mode of the portlets. Basic authentication for the portlets can only be supported if single sign-on is not already enabled between WebSphere
Portal and IBM
Connections. If single sign-on is enabled (through LTPA, Kerberos or another mechanism), it will take precedence. If single sign-on is enabled, the basic authentication credentials entered in the personalize mode of the portlets will be ignored.
Configuring single sign-on for end users is recommended over using basic authentication for end user interactions. When using basic authentication for the portlets, every user must type in their personal credentials manually in the personalize mode of the portlets or shared credentials can be supplied from the Credential Vault. Basic authentication can be especially useful for trials of the portlets before you have a chance to configure some form of single sign-on, but is not recommended for production use.
Parent topic: Deploying the IBM Connections Portlets (Refresh)