Skip to main content
Eptura Knowledge Center

Configure Generic IdP for SSO using SAML 2.0

  1. Last updated
  2. Save as PDF

Eptura to Customer

Eptura will provide the customer with one Ping identifier and one ACS pattern.

Share Value Format
SAML 2.0 Entity ID (Ping)

The Ping base URL configured under System > Server > Protocol Settings > Federation Info > SAML 2.0 Entity ID (same value as the base URL).
Reply URL / ACS URL

{SAML 2.0 Entity ID}/sp/ACS.saml2 (same placeholder as the main page)

There is no separate Eptura-supplied "Audience" string in our PCS guides. The Entra and Okta flows both map IdP UI fields to this same SAML 2.0 Entity ID URL.

IdP-specific field names (same Ping value)

Different products use different labels for the SP entity identifier. The customer must paste the SAML 2.0 Entity ID (Ping base URL) wherever the IdP asks for the SP / application identifier, for example:

  • Microsoft Entra ID: Identifier (Entity ID) / SP Entity ID
  • Okta: Audience URI (SP Entity ID)
  • Other IdPs: Entity ID, SP Entity ID, Audience, Issuer (for the SP side), etc.

If the IdP wizard only asks for ACS URL and Entity ID, those two values above are sufficient; "Audience" is not an extra value from Eptura when following our documented model.

Customer to Eptura

When this is completed, then the customer needs to provide Eptura with the following.

  • Metadata URL or Metadata XML

Additionally, provide the details for the routing/configuration:

  • IdP Entity ID (Issuer) (often in metadata)
  • IdP SSO URL (often in metadata)
  • Login domain(s) for Ping policy / domain selector
  • Attribute / NameID mapping per your IdP-connection steps

What is metadata? Metadata is an XML document containing information necessary for interaction with identity or service providers, e.g. URLs of endpoints, information about supported bindings, identifiers, public keys.