C1 provides identity governance and just-in-time provisioning for PingOne. Integrate your PingOne instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.
This connector is in beta. This means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues.We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.
This page covers the PingOne connector, which syncs and provisions access data for identity governance. It does not control how you sign in to C1. To set up signing in to C1 with your PingOne account, see Authenticate with PingOne.
Configuring the connector requires you to pass in information from PingOne. Gather these configuration details before you move on.Here’s the information you’ll need:
PingOne Client ID
PingOne Client Secret
PingOne Environment ID
See the PingOne docs for information on how to acquire credentials: View the documentationThis connector requires the following scopes:
The Connector Administrator or Super Administrator role in C1
Access to the set of PingOne configuration information gathered by following the instructions above
Cloud-hosted
Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for PingOne and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Enter the configuration information from the previous section.
9
Click Save.
10
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your PingOne connector is now pulling access data into C1.
Follow these instructions to use the PingOne connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Baton and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
In the Settings area of the page, click Edit.
8
Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.
# baton-ping-one-secrets.yamlapiVersion: v1kind: Secretmetadata: name: baton-ping-one-secretstype: OpaquestringData: # C1 credentials BATON_CLIENT_ID: <C1 client ID> BATON_CLIENT_SECRET: <C1 client secret> # PingOne config BATON_PINGONE_CLIENT_ID: <PingOne Client ID for OAuth2 authentication> BATON_PINGONE_CLIENT_SECRET: <PingOne Client Secret for OAuth2 authentication> BATON_PINGONE_ENVIRONMENT_ID: <PingOne Environment ID to list resources from> # Optional: include if you want C1 to provision access using this connector BATON_PROVISIONING: true
See the connector’s README or run --help to see all available configuration flags and environment variables.
Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
2
Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the ping-one connector to. ping-one data should be found on the Entitlements and Accounts tabs.
Done. Your PingOne connector is now pulling access data into C1.
