Enabling single sign-on for Lotus Quickr
Before installing the IBM® Connections Connector for IBM Lotus® Quickr®, enable single sign-on (SSO) between IBM Connections and Lotus Quickr.
Before you begin
- This is an optional task.
- This task applies to Quickr J. For information about enabling single sign-on (SSO) for Quickr D, see the Enabling single sign-on for Domino® topic.
- If you are enabling SSO between IBM Connections and a product that is deployed on a pre-6.1 version of WebSphere® Application Server, you must first complete the steps described in the Enabling single sign-on for stand-alone LDAP topic.
About this task
When your IBM Connections applications are deployed on servers in the same WebSphere Application Server cell, SSO is enabled by default. However, when they applications are hosted in different cells, they use different LTPA certificates and you must manually enable SSO between IBM Connections and Lotus Quickr. To do this, you must exchange LTPA certificates between the cells.
If all the cells use Federated Repositories, set the realm name in each cell to the same value. For example, ensure that all cells use defaultWIMFileBasedRealm or a custom realm name such as exampleRealmName. Set the realm names before you export the LTPA token.
If any cell uses a stand-alone LDAP instead of Federated Repositories, set the realm names of all cells to the name of the LDAP server. For example, if you connect to an LDAP server at ldapserver.example.com over port 389, set all the realm names to ldapserver.example.com:389. Set the realm names before you export the LTPA token.
In either scenario, all cells must use the same realm name to facilitate SSO between the cells.
To allow SSO between IBM Connections and Lotus Quickr, complete the following steps:
Procedure
- On the IBM Connections
Deployment Manager:
- On the node where Lotus Quickr is installed, complete
the following steps:
- Complete the following steps on the system that hosts the
Deployment Manager:
- Restart the Deployment Manager.