# PingOne

> Configure a SAML application in PingOne.

Source: https://diakrin.com/docs/sso/pingone

This guide covers PingOne SAML applications. For PingFederate or another Ping product, use [Other SAML providers](/docs/sso/generic-saml) with your product’s administration guide.

## Create the application

1. In PingOne, open **Applications → Applications** and add a **SAML application** named **Diakrin**.
2. Import the service-provider metadata from your [Diakrin setup packet](/docs/sso#get-your-setup-packet), or enter the ACS and Entity ID manually.
3. Configure an `email` attribute from the directory’s work-email field. Use EmailAddress NameID or an agreed stable Persistent identifier.
4. Select a current signing certificate, use SHA256 signing, and assign only the pilot population.
5. Enable the application and apply the intended authentication policy.

## Map the fields

| PingOne field | Value |
| --- | --- |
| Entity ID / SP Entity ID | Diakrin SP Entity ID |
| ACS URLs | Diakrin ACS URL, using HTTP-POST |
| Application home / sign-on URL | Diakrin console sign-in URL |
| SAML attribute `email` | Work email |
| Subject / NameID | Stable EmailAddress or Persistent identifier |

## Activate and test

Obtain the application’s IdP metadata XML or URL and return it with approved domains and certificate expiry to your Diakrin onboarding contact. If your setup uses a virtual server ID, use the metadata for that same issuer. After activation, run [Test and roll out SSO](/docs/sso/testing).

If assertion validation fails, compare the application’s configured Entity ID and ACS URL to the packet and check the signing certificate’s validity.

Official reference: [Editing a SAML application in PingOne](https://docs.pingidentity.com/pingone/applications/p1_edit_application_saml.html).
