CA SiteMinder® or the SPS federation gateway can act as a SAML 2.0 Service Provider. The Service Provider uses the assertions that it receives from an Identity Provider to authenticate users and then provide access to the requested federation resources. Assuming that the CA SiteMinder® Service Provider has access to a user store at its site, the Service Provider uses the CA SiteMinder® SAML 2.0 authentication scheme to authenticate users.

The SAML 2.0 authentication scheme enables cross-domain single sign-on. The Service Provider is able to consume an assertion from an Identity Provider, identify a user, and establish a CA SiteMinder® session. After a session is established, the Service Provider can authorize the user for specific resources.

The following illustration shows the components for authentication at the Service Provider.

Note: A site can be both an Identity Provider and a Service Provider.

The major components for SAML 2.0 authentication are shown in the following illustration.

Graphic showing the major components required for SAML 2.0 authentication

Note: The SPS federation gateway can replace the Web Agent and Web Agent Option Pack to provide the Federation Web Services application functions. For information about installing and configuring the SPS federation gateway, see the Secure Proxy Server Administration Guide.

The SAML 2.0 authentication scheme is configured at the Policy Server that resides at the Service Provider site. The authentication scheme invokes the Assertion Consumer Service, a component of the Federation Web Services application, that is installed on the Web Agent or SPS federation gateway at the Service Provider site. The service obtains information from the SAML authentication scheme, then uses that information to extract the necessary information from a SAML assertion.

The SAML assertion becomes the user credentials to log in to the Service Provider Policy Server. The user is authenticated and authorized, and if authorization is successful, the user is redirected to the target resource.

The Assertion Consumer Service accepts AuthnRequests that include an AssertionConsumerServiceIndex value of 0. All other values for this setting are denied.

SAML Authentication Request Process

The following illustration shows how the SAML 2.0 authentication scheme processes requests.

Graphic showing the SAML 2.0 Authentication Request Process Flow

The functional flow for authentication is as follows:

A user makes a request for a Service Provider resource. This request goes to the AuthnRequest service at the Service Provider. The request is then redirected to the Identity Provider to obtain a SAML assertion.
The Identity Provider returns a response to the Service Provider.
For HTTP-POST binding, the response contains the assertion. For the HTTP-Artifact binding, the response contains a SAML artifact.
The Assertion Consumer Service at the Service Provider receives the response message and determines whether the POST or Artifact binding is being used.
For the HTTP-Artifact binding, the Assertion Consumer Service sends the artifact to the Identity Provider to retrieve the assertion. The Identity Provider returns a response that contains the assertion. The Assertion Consumer Service uses the response with the assertion as credentials to the Policy Server.
The Policy Server invokes the SAML 2.0 authentication scheme by passing the response message with the user credentials to the scheme to be authenticated.
The user disambiguation process begins.
After the disambiguation phase is complete, the SAML 2.0 authentication scheme validates the credentials in the assertion. The scheme also validates the assertion for time validity, and, if applicable, verifies that a trusted Identity Provider signed the assertion.
Note: For the POST binding, a signature is required. If a signature is not present, authentication fails. For the Artifact binding, a signed assertion is optional because the assertion is obtained over a secure channel between the Service Provider and Identity Provider.

If single logout is enabled, the SLO servlet redirects the user to a No Access URL.

Prerequisites for a Relying Partner

For CA SiteMinder® to act as the relying partner, complete following tasks:

Install the Policy Server.
Install one of the following components:
- The Web Agent and the Web Agent Option Pack. The Web Agent authenticates users and establishes a session. The Option Pack provides the Federation Web Services application. Be sure to deploy the FWS application on the appropriate system in your network.
- The SPS federation gateway, which has an embedded Web Agent and has the Federation Web Services application on the embedded Tomcat web server.
For more information, see the Web Agent Option Pack Guide.
Private keys and certificates are imported for functions that require verification and encrypting of messages.
An asserting partner is set up within the federated network.

How to Configure a SAML 2.0 Authentication Scheme

Configuring a Service Provider requires the following tasks:

Complete the SAML 2.0 authentication scheme prerequisites.
Select the authentication scheme type.
Configure disambiguation to authenticate users.
Configure single sign-on.

Configure a SAML authentication scheme for each Identity Provider that is a federation partner and generates assertions. Bind each scheme to a realm. The realm consists of all the URLs of the target resources requested by users. Protect these resources with a policy.

Tips:

Certain parameter values at the Identity Provider and Service Provider must match for the configuration to work. A list of those parameters is available in Configuration Settings that Must Use the Same Values.
Verify that you are using the correct URLs for the Federation Web Services servlets. The URLs are listed in Federation Web Services URLs Used in SiteMinder Configuration.

Optional Configuration Tasks for a Service Provider

The optional tasks for configuring CA SiteMinder® as a Service Provider are:

Navigating Legacy Federation Dialogs

The Administrative UI provides two ways to navigate to the legacy federation configuration dialogs.

You can navigate in one of two ways:

Following a wizard to configure a new legacy federation object.
When you create an object, a page displays with a configuration wizard. Follow the steps in the configuration wizard to create the object.
Selecting tabs to modify an existing legacy federation object.
When you modify an existing object, a page displays with a series of tabs. Modify the configuration from these tabs. These tabs are the same as the steps in the configuration wizard.

Select the Authentication Scheme Type

The Service Provider uses the identity information in the assertion to authorize access to protected federated resources. A SAML authentication scheme is used for this process.

Before you can assign a SAML 2.0 authentication scheme to protect resources, configure the scheme.

Follow these steps:

Review the SAML 2.0 Authentication Scheme Prerequisites.
Log in to the Administrative UI.
Navigate to Infrastructure, Authentication, Authentication Schemes.
The Authentication Scheme page opens at the General settings.
Name the authentication scheme.
In the Authentication Scheme Type drop-down list, select SAML 2.0 Template. You can also select a protection level for this scheme.
The contents of the Authentication Scheme dialog change to support the SAML 2.0 scheme.
In the Scheme Setup section, click SAML 2.0 Configuration to define the details of the authentication scheme.
If you are configuring the scheme for the fist time, follow the configuration wizard to set up the authentication scheme.

Specify the General Information for the SAML 2.0 Auth Scheme

Identity the Service Provider and Identity Provider in the General settings for the SAML 2.0 authentication schemes.

Follow these steps:

From the main authentication scheme page, click SAML 2.0 Configuration.
If you are modifying an existing scheme, click Modify then click SAML 2.0 Configuration.

The detailed settings for the scheme display.
In the General settings, complete the required fields.
Move on to the User Disambiguation section.