Enabling single sign-on for Tivoli Access Manager with SPNEGO

Configure IBM® Connections to use single sign-on with IBM Tivoli® Access Manager and SPNEGO.

1. Create a user account for WebSEAL in your Active Directory domain. When creating the user account, ensure that you specify the following options:
   • The user cannot change the password
   • The password never expires

   For example, if you create an account for A User, where the Active Directory domain is tamspnego.example.com, the user identity is auser@tamspnego.example.com.

2. Map a Kerberos principal to an Active Directory user. Map the service principal name to the account that you created in Step 1 by running the ktpass command on the domain controller. Use the Tivoli Access Manager server through which users access IBM Connections as the instance in the service principal name.
   1. Run the following ktpass command:

      ktpass –princ SPN -mapuser account_name -mapOp set –pass account_password

      where

      • SPN is the Kerberos service principal name. The host name specified in the SPN should match the host name of the WebSEAL server. For example, if users contact the WebSEAL server at diamond.subnet2.example.com and the WebSEAL server is part of the EXAMPLE.COM Active Directory domain, the Kerberos principal name is HTTP/diamond.subnet2.example.com@EXAMPLE.COM.
      • account_name is the account name that you specified in Step 1.
      • account_password is the password associated with the account that you specified in Step 1.
   2. Modify the Windows service for the WebSEAL instance so that it starts using the new user account that you just created. On the WebSEAL server, complete the following steps:
      1. Click Start > Programs > Administrative Tools > Services.
      2. Right-click on Access Manager WebSEAL-default and select Properties.
      3. Click Log On and then click This account.
      4. Enter the details of the user account and password that you created in Step 1.
      5. Click OK to save your changes.
   3. Grant administrator privileges for the local system to the account that you created in step 1.
3. Enable SPNEGO for WebSEAL:
   1. Stop the WebSEAL server.
   2. Enable SPNEGO over encrypted connections by adding the following lines to the WebSEAL configuration file:

      [spnego]

      spnego-auth = https

      [authentication-mechanisms]

      auth-challenge-type = spnego

      kerberosv5 = fully_qualified_path to the authentication library

      For example: kerberosv5 = TDI_root\bin\stliauthn.dll

      where TDI_root is the installation directory of Tivoli Access Manager.

4. Enable TAI authentication as follows:
   1. In the WebSphere Application Server administrative console, navigate to Security > Global Security > Custom properties > New.
   2. Enter the following name and value pair:

      Name

      com.ibm.websphere.security.performTAIForUnprotectedURI

      Value

      true

   3. Click OK and then click Save to preserve your update.
5. Restart WebSEAL from the Services Control Panel. On Windows, WebSEAL must be running as a service for SPNEGO authentication to work properly. Otherwise, it runs using the credentials of the logged in user.
6. Configure form-based authentication with transparent junctions. Complete all the steps in the Enabling single sign-on for Tivoli Access Manager topic except the steps about updating interService URLs , adding a Tivoli Allow access to the Embedded Experience gadget, and adding a Tivoli Access Manager authenticator property. You need to use the IBM HTTP Server URLs and the DefaultAuthenticator property in this configuration.
   Note: This procedure enables a fallback authentication method for user systems that do not support SPNEGO. This alternative is important for users of Lotus Notes®, mobile devices, and other extensions for IBM Connections.