Skip to content

Enabling SPNEGO single sign-on for SiteMinder

Configure HCL Connections™ to use single sign-on with Computer Associates' SiteMinder and SPNEGO.

Before you can enable SSO, you must first install Connections and ensure that you can access the installed applications from a web browser. You must also have completed the TAI/ASA installation and configuration instructions that are included with SiteMinder, including registering the TAI/ASA with WebSphere® Application Server.

Notes:

  • 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.

  • WebSphere Application Server 7 does not provide the key Java™ libraries that you need to install and configure SiteMinder Application Server Agents (ASA) for WebSphere with WebSphere Application Server. The procedure to update your files is described in Step 1 of this task.
  • 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.

This task describes how to create SiteMinder Agent and Domain objects with realms, rules, and a policy that is related to HTTP Server, Microsoft™ Internet Information Services (IIS), 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. The user is redirected to a Microsoft IIS server which is configured for SPNEGO authentication. If the user provides valid credentials, the user is authenticated by SPNEGO and a SiteMinder agent on the IIS server generates an SMSESSION cookie. This cookie is added to the request which is passed on to WebSphere Application Server. The SiteMinder Trust Association Interceptor (TAI) on the application server verifies the information in the cookie and sets the User Principal that Connections requires to identify the user.

This task refers to 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 with SPNEGO, complete the following steps:

  1. Download and apply the Unrestricted JCE policy files:

    1. Go to the J2SE 5 SDK Security information web page.

    2. Authenticate with your universal HCL 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.

  2. Create agents on the SiteMinder Policy Server, including Web Agents for HTTP Server and Microsoft IIS, 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 HTTP Server.

    4. Repeat these steps for the Web Agent for IIS.

    5. Repeat these steps for the Application Server Agent.

  3. 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 HTTP Server:

      1. Right-click Apache Default Settings Agentand 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 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. While In the SiteMinder Administration Console, set the IgnoreHost parameter either as HTTPS: IgnoreHost="connections.example.com:444" or HTTP:IgnoreHost="connections.example.com:8888" on both the Siteminder Policy server and on the Connections server. If this setting is not the same on both servers, connectivity will fail.

    3. Under the System tab, update the Agent Configuration Object with the following value: FCCCompatMode - NO

    4. Configure the Web Agent for IIS:

      1. Right-click IIS Default Settings Agentand 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 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.

    5. Configure the Application Server Agent:

      1. Right-click Apache Default Settings Agentand 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 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:

    6. When activated, the LogOffUri parameter clears the SMSESSION cookie and ensures that the user is logged out of all Connections browser sessions.

    7. 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.
    8. 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.

    9. Specify your SiteMinder Authentication Scheme configuration:

    10. Open the SiteMinder Administration Console and navigate to the Authentication Scheme Properties dialog box.

    11. From the Authentication Scheme type list, select Windows Authentication template.

    12. Clear the Use Relative Target check box.

    13. Enter the URL of your IIS server in the web Server Name field.

    14. Complete the User DN Lookup field with the appropriate information for your domain. For example, (sAMAccountName=%{UID}).

  4. On the SiteMinder Policy Server, create a domain for the HTTP Server web agent.

  5. Create protected realms under the HTTP Server Web Agent domain:

    1. Using the HTTP Server Agent Object and Windows Authentication Scheme that you created earlier, create SiteMinder realms that are protected by Windows forms authentication.

      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/form/cmis/repository
      Forums /forums/atom/forms
      /forums/follow/atomfba
      Profiles /profiles/atom/forms
      /profiles/atom2/forms
      /profiles/follow/atomfba
      URL Preview /connections/opengraph/form/api/oembed
      /connections/thumbnail/form/api/imageProxy
      Wikis /wikis/follow/atomfba

    2. Using the HTTP Server Agent Object that you created earlier, create SiteMinder realms that are protected by basic authentication.

      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/follow/atom
      Home page /homepage/atom/search
      /homepage/atom/mysearch
      Metrics /metricssc/configsetter
      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/admin/atom
      /profiles/atom
      /profiles/atom2
      /profiles/audio.do
      /profiles/follow/atom
      /profiles/json
      /profiles/photo.do
      /profiles/vcard
      URL Preview /connections/opengraph/basic/api/oembed
      /connections/thumbnail/basic/api/imageProxy
      Wikis /wikis/basic/api
      /wikis/follow/atom

    3. 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.

  6. 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.

  7. Create the following rules for each realm:

    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

  8. 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.

  9. Add the new rules to the new policy.

  10. 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.

    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/
    App Registry /appreg
    /appregistry
    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
    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
    Orient Me /community-suggestions
    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/

  11. On the SiteMinder Policy Server, create a domain for the Application Server Agent.

  12. Add the following realm to the new WebSphere Application Server domain:

    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.

  13. On the SiteMinder Policy Server, create a domain for the IIS Server Agent.

  14. Using the IIS Agent Object and Windows Authentication Scheme that you created earlier, create a SiteMinder realm that is protected by Windows authentication.

    Realm name Protected resource
    IIS_Realm /

  15. Create the following rules for this realm:

    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

  16. 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.

  17. Install the Web Agent on 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.

  18. Install the Web Agent on IIS:

    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.

  19. 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 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.

  20. 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.

  21. 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.

  22. Create rewrite rules that redirect URLs when users log out of 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 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.

  23. For configurations with Connections 4.5 CR1 or later installed, remove the following rewrite rules:

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

    From the SSL and non-SSL sections of the http.conf file, remove the following rewrite rule::

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

  24. Configure SiteMinder to use HTTP or HTTPS communications:

    1. Add the following lines to the end of the httpd.conf file:

      • HTTP:

        Listen 8888
<VirtualHost *:8888>
    ServerName connections.example.com
</VirtualHost>

      • HTTPS:

        Listen 444
<VirtualHost *:444>
    ServerName connections.example.com
    SSLEnable
    Keyfile "/opt/IBM/KeyFiles/webserver-key.kdb"
    SSLStashFile "/opt/IBM/KeyFiles/webserver-key.sth"
</VirtualHost>

        Save and close the file.

    2. Open the WebAgent.conf file, usually located in the ibm_http_server_root/conf directory, and uncomment the LocalConfig.conf location: localconfigfile="/opt/IBM/HTTPServer/conf/LocalConfig.conf". Save and close the file.

    3. Open the LocalConfig.conf file, usually located in the ibm_http_server_root/conf directory, and configure the IgnoreHost setting to ensure that SiteMinder ignores any traffic that goes through this virtual host.

      HTTPS: IgnoreHost="connections.example.com:444"

      HTTP:IgnoreHost="connections.example.com:8888"

    4. Comment out every other line in the LocalConfig.conf file. Save and close the file.

    5. Add the virtual host to WebSphere Application Server:

      1. In the Integrated Solutions Console on the Deployment Manager, click Environment > Virtual Hosts > default_host > Host Aliases > New.

      2. Enter the host name and port of the alias. For example: enter * and 444 for HTTPS, or * and 8888 for HTTP.

        Note: Verify that HTTP Server copied the updated plugin-cfg.xml file to the ibm_http_server_root/Plugins/config/webserver1 directory. The timestamp on the file indicates when it was updated.

    6. Add the interservice URL for the new virtual host to the LotusConnections-config.xml file:

      1. Check out the LotusConnections-config.xml file. For information about editing configuration files, see the Changing common configuration property values topic.
      2. Add 444 or 8888 to each instance of interService URL. For example, change <sloc:interService href="http://connections.example.com"/> to <sloc:interService href="https://connections.example.com:444"/>
      3. Save and check in the file.
      4. Check the LotusConnections-config.xml file to ensure that the custom authenticator already is set to DefaultAuthenticator. If the current configuration has been used previously as a Siteminder configuration but is being enabled for SPNEGO now, then you need to change the custom authenticator property to be DefaultAuthenticator by editing the LotusConnections-config.xml file as follows:

    7. 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 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")

    8. Update the custom authenticator values by running the following commands:

      1. Configure the custom authenticator to support server-to-server authentication for SiteMinder and SPNEGO:

        LCConfigService.updateConfig("customAuthenticator.name",

        "DefaultAuthenticator")

      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.

    9. Check the LotusConnections-config.xml file back in by running the following command:

      LCConfigService.checkInConfig()

  25. Restart HTTP Server, the Deployment Manager, and the nodes.

  26. Files and wikis display the log in button in Siteminder and SPNEGO configuration even though the user is logged in. This occurs in public files and wikis pages as the server does not require user authentication for public pages. To solve this issue, you need to disable anonymous for wikis by mapping 'reader' to 'All authenticated in application's realm'. This change needs to be done for all SPNEGO-related configurations and not just Siteminder and SPNEGO configuration. To remove the log in string for both Files and Wikis on SPNEGO configurations, follow these steps:

    • Log in to the WebSphere Application Server admin console.
    • Go to Applications and click Applications types.
    • Click Websphere enterprise applications, then click Wikis/Files in the list.
    • When the page loads, click User group mapping in Security role pane.
    • Tick box beside Everyone.
    • Click Map special subjects in the drop-down menu, then click All authenicated in application's realm.

    • Click OK, then click Save.

      Note: These steps need to be completed for Files and Wikis. Once the steps are done, restart the configuration to see the changes.

Verify that the configuration is working correctly:

  1. Log in to your Windows client system.
  2. Open Firefox or Internet Explorer and navigate to https://IHS_host/homepage. If you can log in without entering your credentials, then you have successfully configured single sign-on for SiteMinder with SPNEGO.

Parent topic:Configuring single sign-on

Related information

Changing common configuration property values

Changing references to administrative credentials