Learn how to configure a connection to PingFederate via SAML.
Each SSO Identity Provider requires specific information to create and configure a new Connection. Often, the information required to create a Connection will differ by Identity Provider.
To create a PingFederate SAML Connection, you’ll need the Identity Provider metadata that is available from your PingFederate instance.
The ACS URL is the location an Identity Provider redirects its authentication response to. In PingFederate’s case, the ACS URL needs to be set by the Enterprise when configuring your application in their PingFederate instance.
Specifically, the ACS URL needs to be set as the “Endpoint URL” when defining the Protocol Settings in the SP Connection for WorkOS.
The Entity ID is a URI used to identify the issuer of a SAML request, response, or assertion. In this case, the entity ID is used to communicate to that WorkOS will be the party performing SAML requests to the Enterprise’s PingFederate instance.
Specifically, the Entity ID needs to be set as the “Partner’s Entity ID (Connection ID)” when defining the General Info Settings in the SP Connection for WorkOS.
In order to integrate you’ll need the PingFederate IdP metadata.
Normally, this information will come from your Enterprise customer’s IT Management team when they set up your application’s SAML 2.0 configuration in their PingFederate admin dashboard. However, that should not be the case during your setup. Here’s how to obtain them:
Log in to your PingFederate instance, go to the admin dashboard, select “Applications” at the top, and select the “SP Connections” menu option.
On the SP Connection list, find your WorkOS SAML 2.0 connection. Click on the “Select Action” menu and then select “Export Metadata” to download the IdP metadata.
Keep in mind where the file was saved, as we’ll be later uploading it to configure the Connection.
In the SP Connection setup for the WorkOS SAML 2.0 connection, you need to add id, email, firstName, and lastName attributes in the “Browser SSO” menu during the “Assertion Creation” section for the “Attribute Contract”.
How you map values to the attributes listed above may differ based on how your PingFederate instance is set up. Below is an example of mapping values from both an Authentication Policy Contract and an LDAP directory.