About this task
Single sign-on (SSO) enables users to log in to an IBM
Connections application and switch to other applications within the product without having to authenticate again.
There are several different ways to configure SSO. This authentication method allows Tivoli
Access Manager and users web browsers to prove their identities to one another in a secure manner.
Configuring IBM Connections and WebSphere Portal to share a single Deployment Manager saves on administration time by combining administration tasks for the two applications. Establishing a single-sign on environment benefits the users by creating a more seamless environment between the two applications.
Follow these steps to configure single sign-on.
Changing the realm name
- Before federating Portal as a managed node of the Deployment Manager of IBM Connections, make sure the realms match between Connections Deployment Manager and Portal.
If you must change the realm names so they match, follow the steps in Changing the realm name.
- Perform the following steps to collect files from the primary node and copy them to the Deployment Manager:
- From the <wp_profile_root>/ConfigEngine directory of the primary node, run this task: ConfigEngine.bat collect-files-for-dmgr -DWasPassword=password .
This creates a zip file containing all the files which need to be copied to the Deployment Manager. The zip file, named filesForDmgr.zip, will be placed in the <wp_profile_root>/filesForDmgr directory.
- Stop the Deployment Manager.
- Expand each of the files in the filesForDmgr.zip file into the proper location on the Deployment Manager based on the directory names within the zip file. The directory names in the zip file are based on the typical default directory names. The directory called AppServer/profiles/Dmgr01 is used to identify the Deployment Manager profile root, and the AppServer directory is used to identify the Deployment Manager installation root directory. If the Deployment Manager was installed into the default directory (AppServer) and the profile was created in the default directory (AppServer/profiles/Dmgr01), then the zip file can be expanded directly into the directory above the AppServer directory; for example /IBM/WebSphere.
- Start the Deployment Manager.
- To augment a Deployment Manager profile, run the following command from the <AppServer_root>/bin directory:
manageprofiles.bat -augment -templatePath c:/IBM/WebSphere/AppServer/profileTemplates/management.portal.augment -profileName Dmgr01
- Restart the Deployment Manager.
- Add the same Portal administration group as an administrators group on the IBM Connections Deployment Manager.
- Run the following command from the <wp_profile_root>/bin directory to federate the primary node:
addNode.bat dmgr_hostname dmgr_port -includeapps -includebuses
addNode.bat DMhost.cn.ibm.com 8879 -includeapps -includebuses -username adminuser -password adminpwd
- On the Portal server, run syncNode.bat and then restart the Deployment Manager and all node agents.
- To configure the IBM HTTP Server with Single Sign-On, delete and re-add the webserver on the WebSphere Application Server Integrated Solutions Console in order to re-map all applications including Portal, and import the Portal certificate into IBM HTTP Server.
- Configure Tivoli Access Manager on the Portal server, following the directions in the topic Configuring Tivoli Access Manager in the IBM WebSphere® Portal product wiki.
server task default-webseald-TAMhost.cn.ibm.com create -t ssl -b filter -A -F C:\WASLTPA.key -Z password
-h DMhost.cn.ibm.com -c all -f -k -j -J trailer /wpsv70
ConfigEngine.bat run-svrssl-config -Dwp.ac.impl.PDAdminPwd=password
ConfigEngine.bat validate-pdadmin-connection -DWasPassword=password -Dwp.ac.impl.PDAdminPwd=password
ConfigEngine.bat enable-tam-all -DWasPassword=password