Connect Ping Identity services
Ping CLI can connect to multiple Ping Identity products simultaneously, each with its own endpoint and authentication configuration. Connection settings are organized into profiles: each profile holds one connection for each supported product. For example, a development profile might point to a PingOne development tenant and a PingFederate development instance, while a separate sandbox profile connects to sandbox tenants of the same products.
Multiple profiles let you represent different logical environments and switch between them with a single command, without changing any individual service configuration:
pingcli config profiles use sandboxInitialize a connection
The recommended first step when setting up a new profile is the interactive initialization wizard:
pingcli initThe wizard prompts you to select which products to connect, choose an authentication method for each, and enter the required credentials. Your answers are saved to the active profile in ~/.pingcli/config.yaml.
|
Each product connector also exposes its own |
For detailed connection instructions for each product, see the product-specific topics in this section.
PingOne universal service connectors
Several Ping Identity services are universal service connectors: they don’t require their own separate connection setup. Instead, they inherit the credentials and endpoint from the PingOne connector already configured in the profile. To use any of these services, configure the PingOne connector using pingcli pingone init.
| Service | CLI connector name | Connected via |
|---|---|---|
DaVinci |
|
PingOne connector |
PingOne Authorize |
|
PingOne connector |
PingOne Credentials |
|
PingOne connector |
PingOne MFA |
|
PingOne connector |
PingOne Protect |
|
PingOne connector |
PingOne Verify |
|
PingOne connector |
Universal service connectors are accessible as top-level commands (for example, pingcli davinci) and as subcommands of the pingone connector (for example, pingcli pingone davinci).