Enable 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 starting
Notes:
- This is an optional task.
- This task applies to Quickr J. For information about enabling single sign-on (SSO) for Quickr D, see the Enable single sign-on for Domino topic.
- If you are enabling SSO between Lotus Connections and a product that is deployed on a pre-6.1 version of WAS, first complete the steps described in the Enable single sign-on for stand-alone LDAP topic.
About this task
This task describes the steps required to enable SSO between IBM Connections and Lotus Quickr when they are on different websphere Application Server cells. Applications deployed on servers within the same WAS cell are enabled by default for SSO.You should set the realm name in the LTPA token to that of the LDAP server before you export the LTPA token. For example, if you connect to an LDAP server at ldapserver.example.com over port 389, then set the realm name to ldapserver.example.com:389.
To allow SSO between IBM Connections and Lotus Quickr...
Procedure
- On the server where IBM Connections is installed, enable SSO:
- Log into the WAS admin console as an administrator, expand Security -> Global security.
- Expand Web and SIP security and then click Single sign-on (SSO).
- Enter the domain name
.
Note: Ensure that the domain name you enter is valid: On the node where Lotus Quickr is installed, log into the WAS admin console as an administrator, click Security -> Global security -> Web and SIP security -> Single sign-on (SSO) and verify that the domain name is present.
- On the node where Lotus Quickr is installed...
- Log into the WAS admin console as an administrator, and click Security -> Global Security.
- Click LTPA and provide values for the following fields:
- Password – Type a secure password that you will remember. You will need to provide this password later, when you configure to the keys you are exporting
Note: Confirm the password.
- Fully qualified key file name – Specify a valid path and name for the file that will hold the exported keys
- Click Export keys
- On each node where IBM Connections is installed...
- Log into the WAS admin console as an administrator, and click Security -> Global security -> LTPA
- In the Cross-cell single sign-on section, provide values for the following fields:
- Password – Type the password that you used for the Lotus Quickr key file that you exported
Note: Confirm the password.
- Fully qualified key file name – Specify the path and name of the Lotus Quickr key file that you exported
- Click Import keys.
- On each node where IBM Connections is installed...
- Log into the WAS admin console as an administrator.
- Click Security -> Global security -> LTPA, and then in the Cross-cell single sign-on section, provide values for the following fields:
- Password – Type a secure password that you will remember. You will need to provide this password later, when you export the key file
Note: Confirm the password.
- Fully qualified key file name – Specify a valid path and a name for the file that will hold the exported keys
- Click Export keys.
- On the node where Lotus Quickr is installed...
- Log into the WAS admin console as an administrator and click Security -> Global security -> LTPA.
- In the General properties section, provide values for the following fields:
- Password – Type the password that you used for the IBM Connections key file that you exported
Note: Confirm the password.
- Fully qualified key file name – Specify the name of the IBM Connections key file that you exported
- Click Import keys
- Restart all the nodes.
Parent topic
Configure single sign-onRelated concepts
IBM Connections Connector for Lotus Quickr
Related tasks
Enable users to publish file attachments to Lotus Quickr
Enable single sign-on for Domino
Enable single sign-on for standalone LDAP
});