Configure authentication between Portal and Connections for the portlets

Set up single sign-on integration between IBM Connections and WebSphere Portal using third-party security products, or configure basic authentication to enable access to the portlets.

IBM Connections uses single sign-on (SSO) to secure the transfer of user ID and password information. Users can switch to different applications without needing to authenticate again. SSO is automatically enabled when Connections is installed on a single WAS profile or when different profiles are federated into the same cell.

Configure basic authentication to allow 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 Portal and Connections. If single sign-on is enabled (through LTPA, Kerberos or another mechanism), it takes precedence. If single sign-on is enabled, the basic authentication credentials entered in the personalize mode of the portlets are ignored.

If we use 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 useful for trials of the portlets before you have had a chance to configure some form of single sign-on, but is not recommended for production use.

• Enable single sign-on for the portlets for a stand-alone LDAP server
• Configure single sign-on for portlets with TAM and SPNEGO
• Configure single sign-on with Tivoli Access Manager
• Configure single sign-on for portlets with SiteMinder and SPNEGO
• Configure single sign-on for portlets with SPNEGO
• Change the realm name
• Enable basic authentication

Parent topic:
Deploy the Connections Portlets