> ## Documentation Index > Fetch the complete documentation index at: https://docs.gumloop.com/llms.txt > Use this file to discover all available pages before exploring further. # SAML with Ping Identity > Configure SAML single sign-on to Gumloop with PingOne This guide walks a PingOne administrator through connecting Ping Identity to Gumloop for SAML single sign-on. ## Before you start: get your SP details from Gumloop A Gumloop organization admin generates an SSO setup link at [gumloop.com/settings/organization/sso](https://www.gumloop.com/settings/organization/sso) (see [SSO, SAML & SCIM](/enterprise-features/sso_saml_scim)). The setup page shows the two Service Provider values you'll copy into Ping: * **Assertion Consumer Service (ACS) URL** — ends in `/acs` * **SP Entity ID** — the same URL without the `/acs` suffix The same page has the fields for the values Ping produces: **Redirect URL**, **IDP Entity ID**, and the **Certificate** upload. ### Creating an application in PingOne PingOne setup starts from your administrator home page. Exactly how this looks will vary. This example uses a newly provisioned account and therefore shows an onboarding guide; your admin page will look different in most cases. Nonetheless, you'll always start by hitting *Applications* > *Applications* in the left navigation bar. This will take you to a new page.

Once you've navigated to Ping's *Applications* page, press the circular blue button with a plus icon toward the top left. This will trigger a slideover.

Ping wants you to assign the Application an *Application Name*. The name has no impact on the integration, but Ping will use the *Application Name* as the display name. Write "Gumloop" as the *Application Name*.

Then you need to tell Ping that the Application uses SAML. Click the card that reads *SAML Application*. You may notice that this changes the text on the blue button below from *Save* to *Configure*.

Here, select *Configure*. This finalizes creation of the SAML application and progresses you to the next step.

Next, you'll enter some details from Gumloop into Ping. ### Entering Gumloop data in Ping Identity You'll now see a page with a *SAML Configuration* header. It will present three radio button options; of these, select *Manually Enter*. Doing so will trigger two input forms below the radio buttons.

Ping Identity requires two pieces of information about the SAML Connection. Ping first asks for *ACS URLs*. Gumloop provides exactly one — the URL labeled *Assertion Consumer Service (ACS) URL* on your Gumloop SSO setup page. It always ends in `/acs`. Copy the URL from Gumloop and paste it into Ping here.

You'll do something similar again for a field Ping calls *Entity ID*. Gumloop calls this an *SP Entity ID*. You can find it adjacent to the *Assertion Consumer Service (ACS) URL* on the setup page. It matches the *Assertion Consumer Service (ACS) URL* exactly, except it lacks the `/acs` suffix.

Hit *Save* toward the bottom of the page.

### Entering Ping Identity data into Gumloop Now you'll need to enter information about Ping into Gumloop. To start, make sure you're on the *Configure* tab. In a moment, you'll pull three pieces of information from this tab.

Gumloop requires a *Certificate* from Ping. You'll find the appropriate uploader on your Gumloop SSO setup page. To get the file from Ping, click the *Download Signing Certificate* button. Select *X509 PEM (.crt)* from the menu. You'll see a `.crt` file begin to download. The file may have a long and non-descriptive name; that is normal. Upload the file to Gumloop.

After you've taken care of the Certificate, you'll need a field that Gumloop calls an *IDP Entity ID*. It's an input field on the same card as the Certificate uploader. Ping calls this information an *Issuer ID* and places it directly under *Download Signing Certificate* from the previous step. Copy this URL from Ping and paste it into Gumloop as the *IDP Entity ID*.

Finally, look for a field that Ping calls the *Single Signon Service*. Gumloop calls this a *Redirect URL*. Copy the *Single Signon Service* URL and paste it into Gumloop as the *Redirect URL*.

Once you've copied over the *Single Signon Service* URL, you're done swapping information between Gumloop and Ping Identity. Now navigate to the *Attribute Mappings* tab to adjust one final setting in Ping.

### Adjusting Ping attribute mappings Here, you'll see three headers: *Attributes*, *PingOne Mappings*, and *Required*. Where you see *saml\_subject* under *Attributes*, change the corresponding *PingOne Mappings* field. This will trigger a dropdown selector. Make sure you've set this field to *Email Address*.

Hit *Save* at the bottom of the page.

In the top right, change the toggle from *off* to *on*. You're all done!

Please do bear in mind, however, that a Ping admin will still need to assign users to this application before they can sign in.