PingOne
The PingOne sessions of an account seen in a leak are terminated.
How it works
The connection uses a Worker application. PingOne has no bulk session revocation: the user’s open sessions are read and terminated one by one.
Directory matching is separate. PingOne offers SCIM 2.0; the SCIM provider is selected in the panel for matching.
A PingOne access token does not carry the granted permissions in a form that can be read safely. The connection is therefore not marked as verified; the state is shown as it is.
Limits
Passwords are not changed and accounts are not deleted.
Accounts whose identity comes from an external provider are out of scope.
Turning the connection off stops remediation.
Setup
The setup steps are in the panel, on the integration’s own screen. What to do on the provider side and which value goes where is written there.