PingFederate Enterprise Connection
PingFederate can serve as the SAML IdP for AuthAction.
ACS URL
Section titled “ACS URL”In your PingFederate SP connection (or equivalent configuration), set the Assertion Consumer Service (ACS) URL to:
https://<tenant-name>.<region>.authaction.com/oauth2/saml/callbackFields to copy into AuthAction
Section titled “Fields to copy into AuthAction”| Field in AuthAction | Where to find |
|---|---|
| IdP SSO URL | PingFederate admin UI > IdP configuration > SSO Service URL (or your deployment’s sign-on endpoint) |
| Entity ID / Issuer | PingFederate > Server Configuration > Entity ID (IdP entity ID) |
Menu paths can vary by PingFederate version; use your server’s SAML metadata as the source of truth.
Step 1: Configure the connection in PingFederate
Section titled “Step 1: Configure the connection in PingFederate”- Create or edit an SP Connection (or Browser SSO profile) that targets AuthAction.
- Register the ACS URL and SP Entity ID (AuthAction tenant URL).
- Ensure SAML assertions include a suitable Name ID (often email).
- Export or note the IdP SSO URL, Entity ID, and Signing Certificate.
Step 2: Configure PingFederate in AuthAction
Section titled “Step 2: Configure PingFederate in AuthAction”- In AuthAction, go to Connections > Enterprise Connections.
- Select PingFederate.
- Enter the IdP SSO URL and Entity ID / Issuer.
- Add the IdP X.509 certificate if your deployment requires it for signature verification.
- Save.
Step 3: Enable and test
Section titled “Step 3: Enable and test”Enable the connection for your applications and complete a full SSO test.