--- title: "Ping Identity SAML Configuration" slug: "ping-identity-saml-configuration" tags: ["SAML SSO", "Ping Identity"] updated: 2026-10-21T16:11:35Z published: 2026-10-21T16:11:35Z canonical: "docs.eshare.com/ping-identity-saml-configuration" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.eshare.com/llms.txt > Use this file to discover all available pages before exploring further. # Ping Identity SAML Configuration These setup instructions provide information for configuring SAML-based sign-in through Ping Identity (*PingOne or PingFederate*) for all users in the organization to the eSHARE application. The Entity ID and ACS URL referenced in this document will be provided to you by eSHARE’s Customer Success team when the tenant for your organization is provisioned on the eSHARE platform. The following steps will be reviewed: - [Create the SAML Application](/collaborate/docs/ping-identity-saml-configuration#create-the-saml-application) - [Configure SAML Settings](/collaborate/docs/ping-identity-saml-configuration#configure-saml-settings) - [Map User Attributes](/collaborate/docs/ping-identity-saml-configuration#map-user-attributes) - [Send the IdP Details to eSHARE](/collaborate/docs/ping-identity-saml-configuration#send-the-idp-details-to-eshare) - [Assign Users to the Application](/collaborate/docs/ping-identity-saml-configuration#assign-users-to-the-application) - [Configure Group Based Entitlement](/collaborate/docs/ping-identity-saml-configuration#configure-group-based-entitlement) > **REQUIREMENT:** > > The person performing these steps must have administrator access to the **PingOne admin console** or the **PingFederate administrative console**. > [!WARNING] > Note: > > Each section below has separate steps for **PingOne** (*cloud*) and **PingFederate** (*self-managed*). Complete only the steps for your environment. PingID multi-factor authentication is applied to the application in the [Assign Users to the Application](/collaborate/docs/ping-identity-saml-configuration#assign-users-to-the-application) section. ### **Create the SAML Application** **PingOne** 1. Log in to the PingOne admin console and select the correct environment. 2. In the left navigation pane, select '**Applications**' > '**Applications**' (*shown as* '**Connections**' > '**Applications**' *in some versions*) and click the '**+**' (*Add Application*) icon. 3. Enter an '**Application Name**' (*e.g., eSHARE SAML App*). 4. For '**Application Type**', select '**SAML Application**', then click '**Configure**'. 5. Select '**Manually Enter**' and enter the following: 1. For '**ACS URLs**', enter the ***ACS URL*** provided by eSHARE. 2. For '**Entity ID**', enter the ***Entity ID*** provided by eSHARE. 6. Click '**Save**'. **PingFederate** 1. Log in to the PingFederate administrative console. 2. Navigate to '**Applications**' > '**Integration**' > '**SP Connections**' and click '**Create Connection**'. 3. On the '**Connection Template**' tab, select '**Do not use a template for this connection**' and click '**Next**'. 4. On the '**Connection Type**' tab, select '**Browser SSO Profiles**', set '**Protocol**' to **SAML 2.0**, and click '**Next**'. 5. On the '**Connection Options**' tab, leave '**Browser SSO**' selected and click '**Next**'. 6. On the '**Import Metadata**' tab, select '**None**' and click '**Next**'. 7. On the '**General Info**' tab, enter the ***Entity ID*** provided by eSHARE in '**Partner's Entity ID (Connection ID)**', enter a '**Connection Name**' (*e.g., eSHARE SAML App*), and click '**Next**'. ### **Configure SAML Settings** **PingOne** 1. Open the newly created application, select the '**Configuration**' tab, and edit the SAML settings. 2. Verify the following values are selected: 1. '**Subject NameID Format**': **urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress** 2. '**Signing Key**': your active signing certificate, with the assertion and/or response signed 3. '**Assertion Duration**': default value (*leave unchanged unless your policy requires otherwise*) 3. Click '**Save**'. **PingFederate** 1. On the '**Browser SSO**' tab, click '**Configure Browser SSO**'. 2. On the '**SAML Profiles**' tab, select '**SP-Initiated SSO**' (*and* '**IdP-Initiated SSO**' *if users will launch eSHARE from a Ping portal*) and click '**Next**'. 3. On the '**Assertion Lifetime**' tab, keep the default values and click '**Next**'. 4. On the '**Assertion Creation**' tab, click '**Configure Assertion Creation**'. 5. On the '**Identity Mapping**' tab, select '**Standard**' and click '**Next**'. 6. On the '**Attribute Contract**' tab, set the '**SAML_SUBJECT**' subject name format to **urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress**. Leave this tab open and continue with [Map User Attributes](/collaborate/docs/ping-identity-saml-configuration#map-user-attributes). ### **Map User Attributes** **PingOne** 1. Select the '**Attribute Mappings**' tab and click '**Edit**'. 2. Map '**saml_subject**' to **Email Address**. 3. Click '**+ Add**' and enter the following: 1. '**Attributes**': **firstname** 2. '**PingOne Mappings**': select **Given Name** 4. Repeat step 3 to add the following attributes: 1. *Name:* lastname; *value:* Family Name 2. *Name:* email; *value:* Email Address 3. *Name:* upn; *value:* Username (*or the attribute that holds the user's UPN*) 4. *Name:* ncckey; *value:* the attribute holding the Entra ID objectId or some other immutable attribute 5. *Name:* alias; *value:* the secondary email attribute 5. Click '**Save**'. **PingFederate** 1. On the '**Attribute Contract**' tab, under '**Extend the Contract**', add the following attributes, each with the name format **urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified**: **firstname**, **lastname**, **email**, **upn**, **ncckey**, and **alias**. Click '**Next**'. 2. On the '**Authentication Source Mapping**' tab, select '**Map New Authentication Policy**' (*recommended, so PingID applies*) or '**Map New Adapter Instance**'. 3. On the '**Attribute Contract Fulfillment**' tab, map each attribute to its source (*adapter, policy contract, or LDAP/AD data store*): 1. *Name:* SAML_SUBJECT; *value:* mail 2. *Name:* firstname; *value:* givenName 3. *Name:* lastname; *value:* sn 4. *Name:* email; *value:* mail 5. *Name:* upn; *value:* userPrincipalName 6. *Name:* ncckey; *value:* objectGUID or the synchronized Entra ID objectId attribute or some other immutable attribute 7. *Name:* alias; *value:* the secondary mail attribute 1. Complete '**Issuance Criteria**' if required, review the '**Summary**', and click '**Done**', then '**Next**'. 2. On the '**Protocol Settings**' tab, click '**Configure Protocol Settings**'. 3. On the '**Assertion Consumer Service URL**' tab, enter the ***ACS URL*** provided by eSHARE with binding **POST**, mark it as the default, click '**Add**', and click '**Next**'. 4. On the '**Allowable SAML Bindings**' tab, verify '**POST**' is selected. 5. On the '**Signature Policy**' tab, verify the assertion and/or response is signed, complete the remaining tabs, and click '**Done**'. > [!WARNING] > Note: > > Attribute names are case-sensitive and must match exactly. The '**ncckey**' and '**alias**' value mappings may differ depending on which attributes are synced to Ping. Ensure the value mapping selected for '**ncckey**' is any unique and immutable attribute of the user object, and the value mapping for '**alias**' contains any alternative email addresses for the user. Leave the attribute name format as **Unspecified** (*or* **Basic** *if Unspecified is unavailable*). ### **Send the IdP Details to eSHARE** **PingOne** 1. On the application's '**Configuration**' tab, click '**Download Metadata**' (*or copy the* '**IdP Metadata URL**'). 2. Send the metadata file or URL to your eSHARE Customer Success Manager, as they will complete the final steps of the setup. If metadata cannot be shared, send the following instead: 1. Single Signon Service URL 2. Issuer ID 3. X.509 signing certificate (*downloaded from the Configuration tab*) **PingFederate** 1. On the '**Credentials**' tab, click '**Configure Credentials**' and select your IdP signing certificate. 2. On the '**Activation & Summary**' tab, set the connection status to '**Active**' and click '**Save**'. 3. In the '**SP Connections**' list, select '**Export Metadata**' for the eSHARE connection. 4. Send the metadata file to your eSHARE Customer Success Manager, as they will complete the final steps of the setup. If metadata cannot be shared, send the following instead: 1. PingFederate SSO endpoint 2. IdP Entity ID 3. X.509 signing certificate ### **Assign Users to the Application** **PingOne** 1. On the application's '**Policies**' tab, add the sign-on policy that enforces PingID or PingOne MFA. 2. On the '**Access**' tab, add the users and/or groups to whom the application should be assigned. 3. Enable the application using the toggle at the top of the application details. **PingFederate** 1. Verify the PingID adapter (*or the PingOne MFA Integration Kit adapter*) is configured. 2. Navigate to '**Authentication**' > '**Policies**' and verify the policy path used for eSHARE chains your first-factor adapter (*e.g., an HTML form adapter*) to the PingID adapter. 3. Verify the eSHARE SP connection is mapped to that authentication policy contract (*see step 2 of the PingFederate steps in* [Map User Attributes](/collaborate/docs/ping-identity-saml-configuration#map-user-attributes)). ### **Configure Group Based Entitlement** In situations where only a subset of the users authenticated to the eSHARE application should have the ability to share files/folders from their cloud storage service (*e.g., OneDrive, SharePoint, etc.*), it is necessary for Ping to include the Group information of such users. If users are members of the designated Group, the SAML statement sent by Ping to eSHARE during the user’s login would include the Group attribute. This allows eSHARE to consume the Group attribute and enable the cloud storage service. If the Group attribute is not available for the user (because the user is not a member of the Group), such users would be able to access eSHARE but will only be able to access Trusted Shares received by them. To configure Ping to include the Group attribute in the SAML statement: **PingOne** 1. On the application's '**Attribute Mappings**' tab, click '**Edit**'. 2. Click '**+ Add**' and add an attribute (*e.g., groups*) that sends the user's group membership, filtered to the target Group if required. Members of this group would be provisioned with Cloud Provider in the eSHARE application. 3. Click '**Save**'. 4. Send the attribute name and the target Group value to your eSHARE Customer Success Manager. **PingFederate** 1. In the eSHARE SP connection, on the '**Attribute Contract**' tab, extend the contract with a group attribute (*e.g., groups*). 2. On the '**Attribute Contract Fulfillment**' tab, map the group attribute to the data store (*e.g., memberOf*), filtered to the target Group if required. Members of this group would be provisioned with Cloud Provider in the eSHARE application. 3. Save the connection. 4. Send the attribute name and the target Group value to your eSHARE Customer Success Manager.