> For AI agents: [llms.txt](https://docs.trustedauth.com/llms.txt) provides a Markdown index of this documentation.

# SiteMinder

SiteMinder provides policy-based authentication and single sign-on for Web-based applications. See <https://www.broadcom.com/products/identity/siteminder>. You can protect access to SiteMinder by integrating SiteMinder with Identity as a Service. Once integrated, users can use single sign-on to log in to their SiteMinder account through Identity as a Service.

note

This integration was tested using Identity as a Service version 5.33 and SiteMinder 12.8.x version. Other versions of SiteMinder may require integration and configuration steps that differ from those documented in this procedure. In the event of other issues, contact <support@entrust.com> for assistance.

To integrate SiteMinder with Identity as a Service, you must do the following:

Before you begin, open two browser windows. In one window, log in to your SiteMinder administrator account. In the other window, log in to your IDaaS administrator account.

## Step 1: Copy the SAML configurations from Identity as a Service

1. Log into your Identity as a Service administrator account.

2. Click Menu icon **>** **Security > Applications**. The **Applications** **Lists** page appears.

3. Under **SAML Cloud Integrations**, click **SAML Configuration**. The **SAML Configuration** dialog box appears.

   This dialog box contains information you need to configure your SAML application for Identity as a Service authentication.

4. Do one of the following:

   - Leave this dialog box open to reference later in this procedure.
   - Copy the Entity ID, Single Sign-on URL, and Single Logout URL to a text file and save it to reference later in this procedure.

note

Depending on the integration you are performing, you may not need all three of these SAML configuration values.

## Step 2: Copy the SAML signing certificate from Identity as a Service

1. Log in to your Identity as a Service administrator account.

2. Click Menu icon **>** **Security > Applications**. The **Applications List** page appears.

3. Under **SAML Cloud Integrations**, click **SAML Signing Certificates**. The **SAML Signing Certificates** page appears.

4. Click **Copy** next to the certificate to copy it to the clipboard.

   You can additionally download the certificate and save it for future use.

5. Open a text editor, such as Notepad, and paste the contents of the certificate into the text file.

6. Save the file.

note

Be sure to same the file with the `.cer` extension, for example, `SAML_certifcate.cer`.

## Step 3: Configure SiteMinder for Identity as a Service authentication

This integration uses SiteMinder Access Gateway as the local Service Provider and Entrust Identity as a Service as Remote Identity Provider with default settings. There are various combinations to configure a Federation Partnership.

This integration requires the following prerequisites:

- User Directory
- Policy Server
- Access Gateway server details to configure SAML, URLs to Servlets that Initiate Single Sign-on

See the SiteMinder documentation or contact your SiteMinder administrator to configure Federation Partnership.

To configure the prerequisites, you need to create Federation Entities and Federation Partnerships. This involves three steps:

### Step 3.A: Configure Local SAML 2.0 SP Entity

1. Log in to the SiteMinder Administrator console.

2. Go to **Tasks > Federation > Partnership Federation > Entities**. The **Entities** page appears.

3. Click **Create Entity**. The **Select Entity Type** page appears.

4. In the **Select Entity Type** page, do the following:

   1. For the **Entity Location**, select **Local**.
   2. From the **New Entity Type** drop-down list, select **SAML2 SP**.
   3. Click **Next**. The **Configure Entity** page appears.

5. In the **Configure Entity** page, do the following:

   1. In the **Entity ID** field, enter the Entity ID that belongs to the remote partner.

      Example: `https://siteminderaccessgateway.domain.com`

   2. Enter an **Entity Name**.

   3. In the **Description** field, enter a description for the Entity.

   4. In the **Base URL** field enter the base location of the server that is visible to the intended users of the federation. This server is typically the server where SiteMinder is installed.

      Example: `https://siteminderaccessgateway.domain.com`

   note
   Do not put a forward slash at the end of the base URL. A final slash results in two slashes being appended to other URLs that use this base URL.

   5. Expand the **Supported Name ID Formats** and select **Unspecified**.

   6. Leave the remaining settings at the default values.

   7. Click **Next**. The **Confirm** page appears.

6. Open a text editor, such as Notepad and under **Confirm**, copy the following to the text file:

   - **Assertion Consumer Service URL**
   - **Entity ID**

   You need these values in _Step 4: Add SiteMinder to Identity as a Service_.

7. Click **Finish**.

### Step 3.B: Configure Remote SAML 2.0 IDP Entity

1. Log in to the SiteMinder Administrator console.
2. Go to **Tasks > Federation > Partnership Federation > Entities**. The **Entities** page appears.
3. Click **Create Entity**. The **Select Entity Type** page appears.
4. In the **Select Entity Type** page, do the following:
   1. For the **Entity Location**, select **Remote**.
   2. From the **New Entity Type** drop-down list, select **SAML2 IDP**.
   3. Click **Next**. The **Configure Entity** page appears.
5. In the **Entity ID** field, enter the **Entity ID** you copied in _Step 1: Copy the SAML configurations from Identity as a Service_.
6. In the **Description** field, enter a description for the Entity.
7. In the **Remote SSO Service URLs** section, do the following:
   1. From the **Binding** drop-down list, select **HTTP-Redirect**.
   2. In the **URL** field, enter the **Single Sign-on URL** you copied in _Step 1: Copy the SAML configurations from Identity as a Service_.
8. Expand the **Signature and Encryption options** section and do the following:
   1. Click **Import**. The **Select File** page appears.
   2. For the **Input File As**, select **Single Key / Cert File**.
   3. Click **Browse** and browse to select the SAML signing certificate file you downloaded in _Step 2: Copy the SAML signing certificate from Identity as a Service_.
   4. Click **Next**. The **Confirm** page appears.
9. Click **Finish**.

### Step 3.C: Configure Partnerships

1. Log in to the SiteMinder Administrator console.
2. Go to **Tasks > Federation > Partnership Federation > Partnerships**. The **Partnerships** page appears.
3. Click **Create Partnership**.
4. From the **Create Partnership** drop-down list, select **SAML2 SP -> IDP**. The **Configure Partnership** page appears.
5. In the **Configure Partnership** page, do the following:
   1. Enter a **Partnership Name**. For example, `EntrustIDaaSSiteminderPartnership`.
   2. From the **Local SP** list, select the Entity you created in _Step 3.A: Configure Local SAML 2.0 SP Entity_.
   3. From the **Remote IDP** list, select the Remote SAML 2.0 IDP Entity you created in _Step 3.B: Configure Remote SAML 2.0 IDP Entity_.
   4. Set the **Skew Time (Seconds)** to **30**.
   5. Under **User Directories and Search order**, select the user directory configured for the SiteMinder Policy Server and move it to **Selected Directories**.
   6. Click **Next**. The **User Identification** page appears.
6. In the **User Identification** page, do the following:
   1. Select **Use Name ID**.
   2. From the **NameIDPolicy Format** drop-down list, select **Unspecified**.
   3. In the **LDAP Search Specification** field enter the LDAP search specification. This value changes depending on the LDAP used. For example, for ODSEE LDAP, the value is `uid=%s`.
   4. For **Federated Users**, under **User Class**, select **All Users in Directory**.
   5. Leave the remaining settings at the default values.
   6. Click **Next**. The **SSO and SLO** page appears.
7. In the **SSO and SLO** page, do the following:
   1. For the **Authentication Binding Request**, select **HTTP-Redirect**.
   2. For the **SSO Profile**, select **HTTP-POST**.
   3. From the **Issuer Format** drop-down list, select **Unspecified**.
   4. Click **Next**. The **Configure AuthnContext** page appears.
8. Leave the **Configure AuthnContext** settings at the defaults.
9. Click **Next**. The **Signature and Encryption** page appears.
10. In the **Signature and Encryption** page, do the following:
    1. From the **Verification Certificate Alias** drop-down list, select the certificate you imported in _Step 3.B: Configure Remote SAML2.0 IDP Entity_.
    2. Leave the remaining settings at the default values.
    3. Click **Next**. The **Application Integration** page appears.
11. In the **Application Integration** page, do the following:
    1. For the **Redirect Mode : No data** select the default setting.
    2. In the **Target** field, enter the URL that is protected by SAML. This is the resource protected behind the SiteMinder Access Gateway.
    3. Leave the remaining settings at the default values.
    4. Click **Next**. The **Confirm** page appears.
12. Review all settings and then click **Confirm**.

## Step 4: Add SiteMinder to Identity as a Service

1. In Identity as a Service, click Menu icon **>** **Security > Applications**. The **Applications** **Lists** page appears.
2. Click **Add**. The **Select an Application Template** page appears.
3. Do one of the following:
   - Select **SAML Cloud Integrations** from the search drop-down list and scroll to find the application you want to add to IDaaS.
   - In the **Search bar**, enter a search option to filter for the application you want to add to IDaaS.
4. Click **SiteMinder**. The **Add SiteMinder** page appears.
5. Enter an **Application Name**.
6. Enter an **Application Description**.
7. Optional. Add a custom application logo.
   1. Click Plus icon next to **Application Logo**. The **Upload Logo** dialog box appears.
   2. Click Upload icon to select an image file to upload.
   3. Browse to select your file and click **Open**. The **Upload Logo** dialog box reappears showing your selected image.
   4. If required, resize your image.
   5. Click **OK**.
8. Select the **Authentication Flow** that appears to users during login.
9. Click **Next**. The **General** page appears.
10. In the **Default Assertion Consumer URL** field, enter the **Assertion Consumer Service URL**, enter the Assertion Consumer URL you copied from SiteMinder in _Step 3.B: Configure Remote SAML IDP Entity_.
11. In the **Service Provider Entity ID** field, enter:
12. In the **Single Logout Service URL** field, enter the Single Sign-on URL you copied from SiteMinder in _Step 3.B: Configure Remote SAML IDP Entity_.
13. Enter the **SAML Session Timeout** to the time when the SAML Assertion times out. The maximum is 720 minutes.
14. Enter the **Max Authentication Age (seconds)** to set the maximum amount of time that can elapse before a user is required to reauthenticate during a new login attempt. This applies for both SP-initiated and IDP-initiated login. Set this field to -1 to disable this feature.
15. From the **SAML NameID Attribute** drop-down list, select **User ID**.
16. From the **SAML NameID Encoding Format** drop-down list, select **Unspecified**.
17. From the **SAML Signing Certificate** from the drop-down list, select the SAML Signing Certificate that you imported into SiteMinder.
18. Deselect **Enable Go Back Button** if you do not want users to be able to go back to the ReviewInc login page to log in.
19. Select **Show Default Assertion Consumer URL Service in the My Profile**. When selected, the Default Assertion Consumer URL appears in a user's My Profile page in addition to relay states and Alternative Assertion Consumer URLs.
20. Add an **Alternate Assertion Consumer Service URL**
    1. Click **Add**.
    2. Enter a **Name**.
    3. Enter a URL **Value** field. For example, `https://<userID>.<mycompany.com>/SAML20/`
    4. Select **Show in My Profile** to display the Alternative Consumer Service URL in a user's My profile page.
    5. Click **Add**.
21. Leave the remaining settings at the default values.
22. Click **Submit**.

## Step 5: Add a resource rule

See [Create resource rules](/docs/authentication-and-security/create-and-manage-resource-rules.md).

## Step 6: Test the integration

### Testing Service Provider Login

See the Siteminder documentation regarding URLs to Servlets that Initiate Single Sign-on.

Note the following:

- The page with these hard-coded links must reside in an unprotected realm.
- The hard-coded link that the user selects must contain specific query parameters, which are used in an HTTP GET request to the AuthnRequest service.

The syntax for the link is:

Example: `http://sp_server:port/affwebservices/public/saml2authnrequest?ProviderID=idp_id&RelayState=target_URL`

`https://cag.domain.com/affwebservices/public/saml2authnrequest?ProviderID=https://entrust.us.trustedauth.com/api/saml&RelayState=https://cag.domain.com/saml`

To test Service Provider login:

1. Access the hard-coded link to be redirected to the Identity as a Service login page.
2. Log in with your first factor credentials.
3. Respond to the second-factor authentication challenge. If you respond successfully, you are redirected Target URL of SiteMinder.

### Testing Identity as a Service redirect log in

1. Log in to your Identity as a Service account.
2. Go to your **My Profile** page if you are not already there.
3. Under **Applications**, click **SiteMinder**.
4. Respond to the second-factor authentication challenge. If you respond successfully, you are logged in to SiteMinder.