Enable single sign-on for the portlets for a stand-alone LDAP server
Overview
Before installing IBM Connections Portlets for IBM WebSphere Portal , enable SSO.
This task describes the steps required to enable SSO between IBM Connections and WebSphere Portal when they are on different WAS cells. Applications deployed on servers within the same WAS cell are enabled by default for SSO.
Set the realm name in the LTPA token to that of the LDAP server before exporting the LTPA token. For example, if you connect to LDAP server at ldapserver.myco.com over port 389, set the realm name to...
ldapserver.myco.com:389
To change the realm name, see: Change the realm name
Allow SSO between IBM Connections and WebSphere Portal
- On the server where IBM Connections is installed, enable SSO:
- Log on to the WAS console as an administrator, expand...
Security | Global security | Web and SIP security | Single sign-on (SSO)
- Enter the domain name.
To verify the domain name is present, on the node where WebSphere Portal is installed, log in to the WAS console, and go to...
Security | Global security | Web and SIP security | Single sign-on (SSO)
- On Connections dmgr node:
- Log on to the WAS console as an administrator and go to...
Security | Global security | LTPA | Cross-cell single sign-on
...and set...
- Password – We provide this password later, when we export the key file
Confirm the password.
- /path/to/key_file – Path and name for the file that stores the exported keys
- Click Export keys.
- On the node where WebSphere Portal is installed:
- Log on to the WAS console as an administrator and click...
Security | Global security | LTPA
- In the General properties section, set:
- Password – Password used for the Connections key file that you exported
Confirm the password.
- /path/to/key_file – Specify the name of the Connections key file that you exported
- Click Import keys
- Restart all the nodes.
Parent topic:
Configure authentication for the portlets