Ping Identity Devops

PingOne Worker Application and User Configuration

The pingctl utility referenced here has been deprecated and is no longer being maintained. It is recommended to use the Ping CLI utility under active development and support.

With few exceptions, many pingctl commands can be replicated using the pingcli utility, with gaps being addressed based on prioritization.

PingOne Worker Application Configuration

To manage PingOne resources using credentials other than your own, you are required to have a PingOne Worker App.

There are three options to authenticate to PingOne from pingctl:

Additionally, you must set up the proper roles for your Worker App

Authorization Code (w/ PKCE) Flow Settings

The following image shows an example of a Worker App setup for Authorization Code (w/ PKCE) Flow:

Expand Screenshot
pingone worker app authorization code

Implicit Flow Settings

The following image shows an example of a Worker App setup for Implicit Flow:

Expand Screenshot
pingone worker app implicit

Client Credentials Flow Settings

The following image shows an example of a Worker App setup for Client Credentials Flow:

Expand Screenshot
pingone worker app client credentials

Worker App Roles Settings

The following image shows an example of the minimum roles required. Typically, these are set up by default.

Expand Screenshot
pingone worker app roles

PingOne User Config

When using Authorization Code or Implicit Flows, you must sign on with an Administrative user to use the Worker App.

It is important to add the proper administrative roles to the user. The following image shows an example of this configuration:

Expand Screenshot
pingone user roles