Ping SSO

Record your Ping SSO connection as identity & sso evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Ping SSO:

   1. In the PingOne admin console, select the environment Safeguard should read and go to Applications › Applications.
   2. Create a new application of type Worker, then use the toggle to enable it.
   3. In the application details panel, click the Roles tab and add the Identity Data Read Only role (scoped to this environment).
   4. Click the Configuration tab and copy the Client ID, Client Secret, Environment ID and Token Endpoint.
   5. PingOne does not issue a static API token: request an access token from the Token Endpoint with the Client ID and Client Secret (client credentials grant) and paste it, or use the PingOne connector with the worker app credentials.

   Where to find the other values:

   • Base URL (optional): The PingOne API host for your region, matching the domain suffix in the worker app's Token Endpoint.
   • Account / Org / Workspace (optional): The Environment ID on the Worker application's Configuration tab.

   Ping SSO's public documentation does not cover every step.

   Source: docs.pingidentity.com, docs.pingidentity.com, checked 2026-10-07.

2. On Compliance › Connectors, open Ping SSO, click Connect, choose API token and fill in:

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

No automated compliance test reads Ping SSO yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• Identity & SSO connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks