Skip to main content
This integration is currently in beta. PingOne directory users are synchronized with Wirespeed, while audit activities are ingested as informational events as we finalize more detailed mappings.

​
Prerequisites

Before connecting PingOne, make sure you have:
  1. Access to the PingOne admin console for the environment you want to monitor
  2. A PingOne worker application that can use the client_credentials grant
  3. The PingOne environment ID for the environment you want Wirespeed to manage
  4. Roles assigned to the worker application that allow it to manage directory users and read audit activities

​
Step 1: Create a Worker Application

  1. Sign in to the PingOne admin console
  2. Open the environment you want Wirespeed to monitor
  3. Navigate to Applications
  4. Create a new Worker application
  5. Enable the client_credentials grant type
  6. Ensure the Token Endpoint Auth Method is set to Client Secret Basic (this is the default)
  7. Save the application

​
Step 2: Assign the Required Access

  1. Open the worker application you created
  2. Assign the roles needed to:
    • Manage directory users using the Identity Data Admin role at the environment level
    • Read audit activities for the environment
  3. Save the role assignments
You can assign Identity Data Read Only instead if you only want Wirespeed to sync directory users. Select Read Only under advanced options when adding the integration.

​
Step 3: Collect the Connection Details

From the PingOne admin console, copy the following values:
  • Environment ID
  • Client ID
  • Client Secret
  • Region for the environment
Use one of these region codes in Wirespeed:

​
Step 4: Add the Integration in Wirespeed

  1. Log in to Wirespeed
  2. Navigate to Integrations > Add Integration
  3. Select PingOne
  4. Enter the following:
    • PingOne Region: NA, CA, EU, AU, SG, or AP
    • Environment ID
    • Client ID
    • Client Secret
  5. Click Integrate
Wirespeed will exchange your worker application credentials for an access token and begin polling PingOne for new data.
During setup, Wirespeed validates that the worker application can read directory users and audit activities for the selected environment. If either required check fails, the integration will not enable.

​
What Wirespeed Collects

Wirespeed currently ingests the following from PingOne:
  • Directory users
  • Audit activities from the PingOne audit reporting APIs

​
Remediation Actions

With Identity Data Admin access, Wirespeed can:
  • Disable users to prevent authentication
  • Re-enable users to restore authentication
  • Force users with PingOne-managed passwords to change their password at next sign-in
  • Terminate the sessions retained by PingOne for a user
Disabling a user does not terminate existing sessions. Session revocation terminates the sessions returned by PingOne, but does not guarantee revocation of every OAuth token.

​
Troubleshooting

  • If authentication fails during setup, confirm the worker application is configured for client_credentials with the Token Endpoint Auth Method set to Client Secret Basic (not Client Secret Post)
  • If setup fails while validating audit activity access, confirm the selected region and environment ID are correct and the worker application can read audit data in the target environment
  • If setup fails while validating directory user access, assign Identity Data Admin or Identity Data Read Only to the worker application at the environment level
  • If a remediation action fails with a permissions error, confirm the worker application has Identity Data Admin access for the user’s environment or population
  • If you are unsure which region to use, verify the PingOne environment’s regional domain in the admin console and match it to the table above