Troubleshooting SAML 2.0

Review the topics in this section to see if your issue is addressed.

Perform the following steps so that your SAML 2.0 Web SSO support for HCL Connections deployment can collect pertinent trace data.
  1. Test SAML with Snoop. Be sure not to configure Connections until you have done so.
  2. Enable the Security trace as follows:**=off
  3. Enable the directory services trace as follows:*=all
  4. Enable the http client trace as follows:*=all
  5. Enable the redirection services trace as follows:*=all

Disabling SAML to validate fully functioning integration for third party servers

Connections can incorporate many services into Social Business Platform. It is necessary to isolate system-wide security features to validate whether third party servers, such as FileNet® servers, can be deployed properly as a fully functional integrated server with Connections prior to enabling the SAML protection.

Before you begin

Make a record of the exact configuration of custom properties for the SAML TAI by accessing the WebSphere® Application Server Integrated Solutions Console Global security > Trust association > Interceptors. This setting also can be found in the security.xml file, for which you should make a backed-up copy before making any changes.


  1. Select and delete the SAML TAI
  2. Disable SAML TAI, but leave OAuth TAI enabled as follows:
    1. Set InvokeTAIbeforeSSO properties to only.
    2. Remove DeferTAItoSSO properties.
  3. Configure custom authenticator services to use the DefaultAuthenticator as follows:
    1. Check out the LotusConnections-config.xml.
    2. Verify that the XML element <customAuthenticator name="DefaultAuthenticator" /> is specified. If the value is not "DefaultAuthenticator", edit it to be so and then save the file.
    3. Check the file back in.
  4. Run Full Resynchronize for all nodes, and then restart all application server instances.