Enabling single sign-on for SiteMinder

Configure IBM® Connections to use Computer Associates' SiteMinder to implement user authentication and single sign-on (SSO).

Before you begin

Complete the following prerequisite conditions:

Ensure that you can access IBM Connections applications from a web browser.
Complete the installation and configuration of TAI/ASA. The instructions are included with SiteMinder.
Verify that TAI/ASA is registered with WebSphere® Application Server.
Each href attribute in the LotusConnections-config.xml file is case-sensitive and must specify a fully-qualified domain name.
The connectionsAdmin J2C alias that you specified during installation must correspond to a valid account that can authenticate with SiteMinder. It may map to a back-end administrative user account. This account must be capable of authenticating for single sign-on against SiteMinder. If you need to update the user ID or credentials for this alias, see the Changing references to administrative credentials topic.
For more information about the SiteMinder Policy Server and Web Agent configuration, go to the CA SiteMinder BookShelf.
For more information about the SiteMinder Agent for WebSphere, see the CA SiteMinder Agent for WebSphere guide (PDF) and the CA eTrust SiteMinder Agent for IBM WebSphere Release Notes® (PDF). The latest Application Server Agent (ASA) at the moment is version 12. CA support confirms that it can be used with SM 12.51.

About this task

You need to create SiteMinder Agent and Domain objects with realms, rules, and a policy that is related to IBM HTTP Server and WebSphere Application Server.

When a user requests a page that is protected by SiteMinder, the Web Agent on the HTTP server intercepts the request and prompts the user for authentication. If the user provides valid credentials, the user is authenticated and an SMSESSION cookie is added to the request which is then passed on to the WebSphere Application Server. The SiteMinder Trust Association Interceptor (TAI) on the server verifies the information in the cookie and sets the User Principal that IBM Connections requires to identify the user.

This task describes a configuration that uses SiteMinder Policy Server 6.0 SP5, SiteMinder ASA 6.0 Agent for WebSphere Application Server (with CR00010 hotfix), and SiteMinder Web Agent v6qmr5-cr035.

To set up SSO using SiteMinder, complete the following steps:

Procedure

Download and apply the Unrestricted JCE policy files:
1. Go to the J2SE 5 SDK Security information web page.
2. Authenticate with your universal IBM user ID and password.
3. Download the Unrestricted JCE Policy files for SDK for all newer versions package.
4. Extract the files from the downloaded package.
5. Back up your existing copies (if any) of the US_export_policy.jar and local_policy.jar files, located in the app_server_root/java/jre/lib/security directory.
6. Copy the new jar files from the extracted package to the same directory, overwriting any existing files.
Create agents on the SiteMinder Policy Server, including a Web Agent for IBM HTTP Server and an Application Server Agent for WebSphere Application Server.
1. Open the SiteMinder Administration console.
2. Right-click Agents and select Create Agent.
3. Enter details of the Name and Description of the Web Agent for IBM HTTP Server.
4. Repeat these steps for the Application Server Agent.
Create Agent Configuration Objects on the SiteMinder Policy Server. In the SiteMinder Administration Console, open the Agent Conf Objects pane and complete the following steps:
1. Configure the Web Agent for IBM HTTP Server:
  1. Right-click Apache Default Settings Agent and select Duplicate Configuration Object.
  2. Enter the Name and description of the Agent Configuration Object.
  3. Update the following parameters to match your environment:
    
    DefaultAgentName
    
    Name of the Apache Agent created earlier
    
    CookieDomain
    
    your_domain
    where your_domain is your IBM Connections domain. If, for example, the URL is http://activities.example.com/activities, your host name is activities.example.com and your domain is example.com. In this example, you would set CookieDomain=example.com. .
    
    RequireCookies
    
    NO
    This parameter configures the Web Agent to support basic authentication but without requiring all API client programs to support cookies.
    
    BadCSSChars
    
    <,>
    This parameter enables the Invite colleagues functionality in Profiles.
    
    LogOffUri
    
    URI
    Configure SiteMinder to recognize only one web address as the logout web address. Uncomment one of the following URIs by removing the number sign (#) character:
    #LogOffUri="/activities/service/html/ibm_security_logout"
    #LogOffUri="/blogs/ibm_security_logout"
    #LogOffUri="/communities/communities/ibm_security_logout"
    #LogOffUri="/dogear/ibm_security_logout"
    #LogOffUri="/files/ibm_security_logout"
    #LogOffUri="/forums/ibm_security_logout"
    #LogOffUri="/homepage/web/ibm_security_logout"
    #LogOffUri="/moderation/ibm_security_logout"
    #LogOffUri="/news/ibm_security_logout"
    #LogOffUri="/profiles/ibm_security_logout"
    #LogOffUri="/search/ibm_security_logout"
    #LogOffUri="/wikis/ibm_security_logout"
2. Under the System tab, update the Agent Configuration Object with the following value: FCCCompatMode - NO
3. Configure the Application Server Agent:
  1. Right-click Apache Default Settings Agent and select Duplicate Configuration Object.
  2. Enter the Name and description of the Agent Configuration Object.
  3. Update the following parameters to match your environment:
    
    DefaultAgentName
    
    Name of the Apache Agent created earlier
    
    CookieDomain
    
    your_domain
    where your_domain is your IBM Connections domain. If, for example, the URL is http://activities.example.com/activities, your host name is activities.example.com and your domain is example.com. In this example, you would set CookieDomain=example.com.
    
    AssertionAuthResource
    
    /siteminderassertion
    
    AssertbyUserID
    
    True
  4. Check whether the PrevalidateCookie property exists in the Configuration Values as follows:
    - If PrevalidateCookie does exist, click Edit and set it to YES.
    - If PrevalidateCookie does not exist, click Add, add a parameter named PrevalidateCookie, and set it to YES.
    - Click OK and then click OK again to save the parameters.
Notes:
- When activated, the LogOffUri parameter clears the SMSESSION cookie and ensures that the user is logged out of all IBM Connections browser sessions.
- To add parameters, edit the Agent Configuration Object on the SiteMinder Policy Server. Alternatively, you can edit the LocalConfig.conf file on the HTTP server if the Web Agent is configured to use it.
- If you are editing the SiteMinder configuration file directly, you must surround the values of SiteMinder configuration parameters with quotation marks ("); for example: BadCSSChars="<,>". If you are changing these parameters within the SiteMinder Policy Server, do not use quotation marks.
Specify your SiteMinder Authentication Scheme configuration:
1. Open the SiteMinder Administration Console and navigate to the Authentication Scheme Properties dialog box.
2. From the Authentication Scheme type list, select HTML Form template.
3. Clear the Use Relative Target check box.
4. Enter the URL of your IBM Connections HTTP server in the web Server Name field.
On the SiteMinder Policy Server, create a domain for the IBM HTTP Server web agent.

Create protected realms under the IBM HTTP Server Web Agent domain:

Using the Agent Object and Forms Authentication Scheme that you created in Step 3.a and Step 4, create SiteMinder realms that are protected by forms authentication.

See the Realms that require forms authentication table for a list of URLs that are protected by forms authentication.

Table 1. Realms that require forms authentication
This table shows all Connections applications with protected URL resources
Application	Protected URL resource
ConnectionsDefaultRealm	/
Activities	/activities/follow/atomfba
	/activities/service/atom2/forms
	/activities/service/atom2/communityEvent
	/activities/service/download/forms
	/activities/service/getnonce/forms
Blogs	/blogs/api_form
	/blogs/atom_form
	/blogs/follow/atomfba
	/blogs/roller-ui/blog
	/blogs/roller-ui/feed_form
	/blogs/roller-ui/rendering/api_form
	/blogs/roller-ui/rendering/feed_form
	/blogs/roller-ui/BlogsWidgetEventHandler.do
	/blogs/services/atom_form
Bookmarks	/dogear/atom_fba
Common resources	/connections/opensocial/rest
	/connections/config
Communities	/communities/calendar/atom_form
	/communities/follow/atomfba
	/communities/forum/service/atom/forms
	/communities/recomm/ajax
	/communities/recomm/atom_form
	/communities/service/atom/forms
Files	/files/follow/atomfba
Files	/files/form/cmis/repository
Forums	/forums/atom/forms
Forums	/forums/follow/atomfba
Metrics	/metrics
	/cognos
	/cognos/servlet/ping
Profiles	/profiles/atom/forms
	/profiles/atom2/forms
	/profiles/follow/atomfba
URL Preview	/connections/opengraph/form/api/oembed
URL Preview	/connections/thumbnail/form/api/imageProxy
Wikis	/wikis/follow/atomfba

Using the Agent Object and Forms Authentication Scheme that you created in Step 3.a and Step 4, create SiteMinder realms that are protected by basic authentication.

See the Realms that require basic authentication table for a list of URLs that are protected by basic authentication.

Table 2. Realms that require basic authentication
This table shows all Connections applications with protected URL resources
Application	Protected URL resource
Activities	/activities/follow/atom
	/activities/service/download
	/activities/service/html/autocompleteactivityname
	/activities/service/html/autocompleteentryname
	/activities/service/html/autocompletemembers
	/activities/service/atom
	/activities/service/getnonce
Blogs	/blogs/api
	/blogs/atom
	/blogs/follow/atom
	/blogs/issuecategories
	/blogs/roller-ui/feed
	/blogs/roller-ui/rendering/api
	/blogs/roller-ui/rendering/feed
	/blogs/services/atom
Bookmarks	/dogear/api/app
	/dogear/api/deleted
	/dogear/api/notify
	/dogear/atom
Common resources	/connections/opensocial/basic/rest
Communities	/communities/calendar/atom
	/communities/calendar/handleEvent
	/communities/calendar/ical
	/communities/follow/atom
	/communities/forum/service/atom
	/communities/recomm/atom
	/communities/recomm/handleEvent
	/communities/service/atom
	/communities/service/json
Content Manager	/dm/atom/seedlist
Files	/files/basic/api
	/files/basic/cmis
	/files/basic/opensocial
	/files/follow/atom
Forums	/forums/atom
Forums	/forums/follow/atom
Home page	/homepage/atom/search
Home page	/homepage/atom/mysearch
News	/news/atom/service
	/news/atom/stories/newsfeed
	/news/atom/stories/public
	/news/atom/stories/saved
	/news/atom/stories/statusupdates
	/news/atom/stories/top
	/news/atom/watchlist
	/news/atomfba/stories/public
Profiles	/profiles/atom
	/profiles/atom2
	/profiles/audio.do
	/profiles/follow/atom
	/profiles/json
	/profiles/photo.do
	/profiles/vcard
URL Preview	/connections/opengraph/basic/api/oembed
URL Preview	/connections/thumbnail/basic/api/imageProxy
Wikis	/wikis/basic/api
Wikis	/wikis/follow/atom

Optional: Protect login credentials with encryption: Using the Basic over SSL Template scheme, create a SiteMinder Authentication Scheme and apply the new Authentication Scheme to all the SiteMinder realms that require basic authentication.

Create Delete and Head actions for the Web Agent. By default, the Web Agent has only the Get, Post, and Put actions available. To add the Delete and Head actions, complete the following steps:
1. In the SiteMinder Administration Console, click View and select Agent Types.
2. Select Agent Types in the Systems pane.
3. Double-click Web Agent in the Agent Type list.
4. In the Agent Type Properties dialog box, click Create.
5. Enter Delete in the New Agent Action dialog box and click OK.
6. Enter Head in the New Agent Action dialog box and click OK.
7. Click OK again to save the new action.

Create the following rules for each realm:

Table 3. Rules for the IBM HTTP Server realms
GetPostPutDelHead rule	OnAuthAccept rule
Realm: CurrentRealm	Realm: CurrentRealm
Resource: * (not /*)	Resource: * (not /*)
Action: Web Agent actions -> Get,Post,Put,Delete,Head	Action: Authentication events -> OnAuthAccept
When this Rule fires: Allow Access	When this Rule fires: Allow Access
Enable or Disable this Rule: Enabled	Enable or Disable this Rule: Enabled

Create a policy and add the users who will be able to access the server to the policy. You can allow all users in the LDAP directory or a subset of users; for example: an LDAP branch, individual users, or groups of users.
Add the new rules to the new policy.

Specify realms that are not protected by SiteMinder.

Note: You must configure notification templates and some Atom feeds as unprotected URLs. The Blogs footer page must also be unprotected because Blogs uses the Velocity template to extract footer pages.

Table 4. Realms that do not require authentication
This table shows all Connections applications with unprotected URL resources
Application	Unprotected URL resource
Activities	/activities_content
	/activities/auth
	/activities/images
	/activities/oauth
	/activities/service/html/images
	/activities/service/html/mainpage
	/activities/service/html/styles
	/activities/service/html/themes
	/activities/service/html/servermetrics
	/activities/service/html/serverstats
	/activities/serviceconfigs
	/activities/static/
Blogs	/blogs/oauth
	/blogs/serviceconfigs
	/blogs/static/
Bookmarks	/dogear/oauth
	/dogear/peoplelike
	/dogear/serviceconfigs
	/dogear/static/
Common resources	/connections/bookmarklet/tools/blet.js
	/connections/bookmarklet/tools/discussThis.js
	/connections/bookmarklet/tools/rlet.js
	/connections/core/oauth
	/connections/oauth
	/connections/resources/ic
	/connections/resources/socmail-client
	/connections/resources/socpim
	/connections/resources/web
	/connections/rte
	/nav/common
Communities	/communities/calendar/Calendar.xml
	/communities/calendar/oauth
	/communities/comm.widget
	/communities/images
	/communities/nav
	/communities/recomm/oauth
	/communities/recomm/Recomm.xml
	/communities/resourceStrings.do
	/communities/service/atom/oauth
	/communities/service/html/communityview
	/communities/service/html/community/autoCompleteMembers.do
	/communities/service/html/singleas
	/communities/service/json/oauth/
	/communities/service/opensocial/oauth
	/communities/serviceconfigs
	/communities/static/
	/communities/stylesheet
	/communities/tools/embedAS.html
	/communities/widgets
Content Manager	/wsi
	/acce
	/dm
Files	/files/app
	/files/basic/anonymous/api
	/files/basic/anonymous/cmis
	/files/basic/anonymous/opensocial
	/downloadfiles
	/files_content
	/files/form/anonymous/api
	/files/form/anonymous/cmis
	/files/form/anonymous/opensocial
	/files/oauth
	files/serviceconfigs
	/files/static
Forums	/forums/oauth
	/forums/serviceconfigs
	/forums/static/
Home page	/homepage/oauth
	/homepage/search
	/homepage/serviceconfigs
	/homepage/static/
	/homepage/web/updates/
Libraries	/library_content_cache
Metrics	/metrics/service/eventTracker
	/metrics/service/oauth
	/cognos/servlet
Mobile	/mobile_content
Moderation	/moderation/app
	/moderation/oauth
	/moderation/static
News	/help
	/news/common/sand/static/
	/news/follow/oauth
	/news/microblogging/isPermitted.action
	/news/oauth
	/news/serviceconfigs
	/news/sharebox/config.action
	/news/static/
OAuth Provider	/oauth2
Profiles	/profiles/atom/forms/connections.do
	/profiles/images
	/profiles/oauth
	/profiles/serviceconfigs
	/profiles/static/
	/profiles/widget-catalog
Search	/search/atom/search
	/search/oauth
	/search/static/
URL Preview	/connections/opengraph/form/anonymous/api/oembed
	/connections/opengraph/basic/anonymous/api/oembed
	/connections/opengraph/oauth/anonymous/api/oembed
	/connections/thumbnail/api/imageProxy
Widget container	/connections/opensocial/anonymous/rest
	/connections/opensocial/common
	/connections/opensocial/gadgets
	/connections/opensocial/ic
	/connections/opensocial/oauth
	/connections/opensocial/rpc
	/connections/opensocial/social
	/connections/opensocial/xrds
	/connections/opensocial/xpc
Wikis	/wikis/basic/anonymous/api
	/wikis_content
	/wikis/form/anonymous/api
	/wikis/home
	/wikis/js
	/wikis/oauth
	/wikis/static/

Map the Reader role in the Activities and Wikis applications All Authenticated in Application's Realm.
See Roles.
On the SiteMinder Policy Server, create a domain for the Application Server Agent.
Add the following realm to the new WebSphere Application Server domain:
Table 5. SiteMinder realms for WebSphere Application Server

Realm name Protected resource

SM TAI Validation /siteminderassertion

Note: You must configure the Protected Resource of this realm to match the AssertionAuthResource parameter that you configured earlier for the Application Server Agent.
Note: Make sure that SM TAI honors SM session-based cookies and the triggered LTPA cookies to be generated by WAS.
Set the timeout value of the session for each realm.
1. In the SiteMinder Policy Server, open the Realm Dialog and click Session.
2. In the Session Timeouts Group Box, enter timeouts for each realm. Enter the following values, if they are not already present:
  
  Maximum Timeout Enabled
  
  2 Hours 0 Minutes
  
  Idle Timeout Enabled
  
  1 Hours 0 Minutes
Note: The maximum timeout and the idle timeout must be longer than the LTPA token timeout, which is defined in WebSphere Application Server. The LTPA token timeout is set to 120 minutes by default.
Install the Web Agent on IBM HTTP Server:
1. Download the latest version of the Web Agent from the CA website.
2. Install the Web Agent. For instructions, go to the SiteMinder BookShelf.
3. When you are prompted for the Agent Configuration details, specify the Agent Configuration Object that you created earlier.
Install the Application Server Agent on your WebSphere nodes:
1. Download the latest version of the Application Server Agent from the CA website.
2. Install the Application Server Agent on each node in your IBM Connections deployment. For instructions, see the SiteMinder Agent for WebSphere Agent Guide.
3. When you are prompted for the Agent Configuration details, specify the Agent Configuration Object that you created earlier.
Copy the smagent.properties file from the ASA installation conf folder to the WebSphere Application Server profile properties folder; for example: C:\program files\IBM\websphere\appserver\profiles\appsvr01\properties.

Note: If Cognos® is enabled, also copy the smagent.properties file to the properties folder of the WebSphere Application Server profile that hosts Cognos.
Configure Trust Association Interceptor on WebSphere Application Server.
1. From the administrative console for WebSphere Application Server, click Security > Global security.
2. Under Web and SIP security, click Trust association.
3. Click Enable Trust Association and then click Save.
4. Click Interceptors.
5. Delete any unused interceptors.
  Note: Do not delete the OAuth interceptor.
6. Click New and enter the following name for the new interceptor:
  com.netegrity.siteminder.websphere.auth.SmTrustAssociationInterceptor
7. Add the following custom property under Global Security > Custom properties: com.ibm.websphere.security.performTAIForUnprotectedURI=true.
8. Click OK and then click Save.
  Note: Connections servers should be protected by both SM TAI and OAuth TAI. This is important for supporting the EE and Activities Stream features.
9. Restart WebSphere Application Server.

Table 5. SiteMinder realms for WebSphere Application Server
Realm name	Protected resource
SM TAI Validation	/siteminderassertion

Create rewrite rules that redirect URLs when users log out of IBM Connections. Add the following rules to the httpd.conf file:

RewriteEngine On

RewriteCond %{REQUEST_URI} /(.*)/ibm_security_logout(.*)

RewriteCond %{QUERY_STRING} !=logoutExitPage=your_logout_url

RewriteRule /(.*)/ibm_security_logout(.*)

LogOffUri?logoutExitPage=your_logout_url [noescape,L,R]

where LogOffUri is the URL that you uncommented earlier. After logging out of IBM Connections, the user's browser is directed to your_logout_url. This URL could be your corporate home page or the SiteMinder login page.

Note: You must add these rules to both the HTTP and HTTPS entries.

The following example illustrates a typical portion of the httpd.conf file after you have implemented this step:

RewriteEngine on
RewriteCond %{REQUEST_URI} /(.*)/ibm_security_logout(.*)
RewriteCond %{QUERY_STRING} !=logoutExitPage=http://corphome.example.com
RewriteRule /(.*)/ibm_security_logout(.*)  /homepage/web/ibm_security_logout?logoutExitPage=http://corphome.example.com [noescape,L,R]


RewriteCond %{REQUEST_URI} !^/blogs/roller-ui/rendering/(.*)
RewriteRule ^/blogs/(.*)/feed/blogs/atom(.*) /blogs/roller-ui/rendering/feed/$1/blogs/atom/ [R,L]

#Connections Config for SSL
LoadModule ibm_ssl_module modules/mod_ibm_ssl.so
<IfModule mod_ibm_ssl.c>
Listen 0.0.0.0:443
<VirtualHost *:443>
ServerName connections.example.com
SSLEnable
RewriteEngine on
RewriteCond %{REQUEST_URI} /(.*)/ibm_security_logout(.*)
RewriteCond %{QUERY_STRING} !=logoutExitPage=http://corphome.example.com
RewriteRule /(.*)/ibm_security_logout(.*) /homepage/web/ibm_security_logout?logoutExitPage=http://corphome.example.com [noescape,L,R]


RewriteCond %{REQUEST_URI} !^/blogs/roller-ui/rendering/(.*)
RewriteRule ^/blogs/(.*)/feed/blogs/atom(.*) /blogs/roller-ui/rendering/feed/$1/blogs/atom/ [R,L]

</VirtualHost>
</IfModule>
SSLDisable

Note: Uncomment the

LoadModule
rewrite_module modules/mod_rewrite.so

line in the httpd.conf file. This line is commented out by default. When the line is commented out, the web server will not start.

If you're using Cognos, you must disable the MBean to enable the metrics. In the WebSphere Application Server Integrated Solutions Console, click Security > Global Security > Custom Properties. Then click New to add the following custom property.
```
com.ibm.websphere.security.disableGetTokenFromMBean=false
```
Save and close the httpd.conf file, restart the HTTP server, and then make sure the SiteMinder page displays when users access the http server.
Add a SiteMinder authenticator property to the IBM Connections configuration by editing the LotusConnections-config.xml file.
1. Use the following command to check out the configuration file:
  - execfile("app_server_root/profiles/DMGR/bin/connectionsConfig.py")
    Note: If you are prompted to specify which server to connect to, enter 1.
    LCConfigService.checkOutConfig("working_directory","cell_name")
  where:
  - app_server_root is the WebSphere Application Server installation directory
  - DMGR is the name of the Deployment Manager profile. For example: Dmgr01
  - working_directory is the temporary working directory to which the configuration XML and XSD files are copied while you edit them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.
  - cell_name is the name of the WebSphere Application Server cell hosting the IBM Connections application. This argument is case sensitive. If you do not know the cell name, execute the following command in the wsadmin client to determine it:
    
    print AdminControl.getCell()
  For example:
  LCConfigService.checkOutConfig("c:/temp","foo01Cell01")
2. Update the custom authenticator values by running the following commands:
  1. Configure the custom authenticator to support server-to-server authentication for SiteMinder:
    LCConfigService.updateConfig("customAuthenticator.name",
    "SiteMinderAuthenticator")
  2. Set the value of the custom.authenticator.cookieTimeout parameter to be equal to or less than the maximum timeout and idle timeout values that you configured earlier. Specify the timeout value in minutes.
    LCConfigService.updateConfig("customAuthenticator.CookieTimeout","timeout"
    where timeout is a value in minutes that is less than or equal to the SiteMinder timeout values.
  Note: When your production environment is ready, set the AllowSelfSignedCerts parameter to false.
3. Check the LotusConnections-config.xml file back in by running the following command:
  LCConfigService.checkInConfig()
Restart your IBM Connections deployment.
1. Stop IBM Connections servers, node agents, and deployment manager.
2. Start the deployment manager and nodes.
3. Allow time for the nodes to synchronize, and for the updated LotusConnections-config.xml file to be copied to each node.
4. Start IBM Connections.

What to do next

Advise your users to close all browser windows when they log out of Activities. This precaution avoids potential security problems that could arise because the SiteMinder session cookie in a browser window might still be updating while a user is logging out from a different browser window.