# Other SAML providers

> Map the common SAML settings for another identity provider.

Source: https://diakrin.com/docs/sso/generic-saml

Use this checklist for a SAML 2.0 identity provider without a dedicated guide, including AD FS and PingFederate. Your Diakrin onboarding contact must review compatibility and complete a pilot before activation is treated as ready.

## Configure the service provider

Import the SP metadata in your [setup packet](/docs/sso#get-your-setup-packet) when the identity provider supports it. Otherwise map these fields manually.

| Your provider may call it | Use this value |
| --- | --- |
| Audience, relying-party identifier, SP Entity ID | Diakrin SP Entity ID |
| Reply, callback, recipient, assertion consumer URL | Diakrin ACS URL |
| Sign-on, application home, start URL | Diakrin console sign-in URL |
| Subject or NameID | Stable EmailAddress or Persistent identifier |
| Email claim or attribute | Work email; use `email` or tell Diakrin its exact claim name |
| Response binding | HTTP-POST |

Configure signed assertions with a current certificate and SHA256 signing. Restrict application access to your pilot population. Keep MFA requirements in your organization’s identity policy.

## Share the identity-provider configuration

Provide the IdP metadata URL or XML, approved work-email domains, stable issuer/Entity ID, email claim name and certificate expiry through your agreed onboarding channel. Metadata must describe the intended IdP; a service-provider descriptor cannot replace it.

A private metadata URL that Diakrin cannot reach requires an XML-file handoff. Browsers still need to reach the IdP sign-in page. Do not expose a private identity service merely to complete this setup.

## Confirm compatibility

Start the pilot from the console’s company SSO form. Test the exact issuer, assertion signature, audience, recipient, email and stable identifier. Follow [Test and roll out SSO](/docs/sso/testing).

Direct OIDC federation, SCIM, automatic group-to-role mapping and global SAML logout are outside this onboarding flow. Discuss these requirements before choosing a rollout date.
