---
title: "exSsoSamlSp"
canonical: "https://help.agiloft.com/space/HELP/65275328/exSsoSamlSp"
format: markdown
---
The Service Provider Details tab contains details like the Entity ID and ACS endpoint values you need to supply to the IdP in order to set up Agiloft CLM as a service provider. It also includes options for configuring how users are matched to the IdP for identification and how Login is set if new users are provisioned.

1. Go to the Service Provider Details tab.
2. Start by noting the values that are automatically populated:
  - **Agiloft (SP) Entity Id**: The unique value that identifies the application to your IdP. Typically, you need to edit this value as follows:
    - Add `https://` to the beginning of the string if it isn't already there.
  - **SAML V2 Assertion Consume Service (ACS) Endpoint**: The reply URL where the IdP sends SAML assertions.
  - **Single Sign-On URL**: The URL to use to access Agiloft CLM via SAML SSO.
3. Next, supply the Java KeyStore file path, password, and alias for your Agiloft CLM server. If your KB is hosted by Agiloft and you don't have this information, [contact Support](https://www.agiloft.com/support-login.htm). If your KB is self-hosted, you may need to [generate a key pair](#generate_keystore).
4. In the "Name identifier in SAML Assertion sent by IdP" field, select the format of the NameID the IdP sends in the SAML assertion: User Name, Email Address, or Federation ID. This setting defines the field to match when verifying a user's identity. It also defines the Login value to set when provisioning new users.
  - If you select User Name, the NameID sent from the IdP is matched to the Login field for identification.
  - If you select Email Address, the NameID is matched to the Email field for identification.
  - If you select Federation ID, a drop-down list is presented. Select the field to match to the NameID for identification.

> ℹ️ Your IdP may allow you to customize the format of the NameID attribute. When selecting the value in Agiloft CLM, keep the following notes in mind:
> ℹ️ 
> ℹ️ - If you customize the IdP format, you may need to return to this tab and change the setting to match the IdP.
> ℹ️ - When customizing the IdP, make sure you choose a format that Agiloft CLM supports: username, email address, or ID.

5. Next, for Name Identifier location in SAML Assertion, select the type of XML tag the IdP sends the NameID value in.
  - Typically, the IdP sends a NameID tag like the example below. If your IdP sends a NameID tag, accept the Default value or select NameID TAG from the drop-down list.
  - If your IdP sends NameID in an attribute tag like the example below, select Attribute TAG from the drop-down list. Then enter the Name or FriendlyName for the tag in the "Value of either Name / FriendlyName Field of Attribute tag" field. For example, for the following attribute tag, the Name value is specified:
    
6. Now, select the desired SAML Authentication Profile. This option controls how users gain access to Agiloft CLM via the IdP.
  - **Default**: Users who are already logged in to the IdP can access Agiloft CLM without being prompted to log in. Users who don't have a valid IdP session are prompted to log in.
  - **Passive Web Single Sign On with IdP**: Only users who have a valid IdP session can access Agiloft CLM. Users who aren't logged in to the IdP receive an error message and can't access the system until they log in to the IdP.
  - **Forced Authentication**: Requires users to log in with the IdP every time they access Agiloft CLM, even if they already have a valid IdP login session.
7. Click Finish to save your work.