S2: Enabling SSO between Connections and Quickr

To enable single sign-on (SSO) between Lotus Connections and Lotus Quickr, an LTPA token should be exported from the deployment manager and imported into the Quickr portal console. For instructions, see the information center at:

http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/index.jsp?topic=/com.ibm.connections.25.help/t_secure_sso_quickr.html

It is also important that the SSO domain is set in the deployment manager. This was set to ".example.com" in the preinstallation steps described in S2: Configuring WebSphere Application Server profiles.

To prevent WebSphere Application Server regenerating LTPA tokens at specified intervals (every 12 weeks by default). It is recommended to uncheck the "Automatically Generate Keys" option on the deployment manager console. Note that if this action is not undertaken then new LTPA keys will be generated every 12 weeks resulting in the SSO not working between the two products unless the new key is also shared with the Quickr server.

Finally, it is important that the clocks are within five minutes of each other on the Quickr and Connections machines. After these changes are made, you should restart the Quickr and Connections servers. To verify that SSO is enabled, log into Connections (using a clean browser containing no cookies) and then type the Quickr URL into the Web address. If you remain logged into the Quickr page, SSO is working.

Go to the next topic: