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.
Capabilities
Gather PingFederate credentials
Configuring the connector requires you to pass in credentials generated in PingFederate. Gather these credentials before you move on.
To set up the PingFederate connector, you’ll need:
- Account username and password
- PingFederate domain, in
https://pingfederateserver.com format
Done. Next, move on to the connector configuration instructions.
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in C1
- Access to the set of PingFederate credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by C1.In C1, navigate to Apps > Connectors and click Add connector.
Search for PingFederate and click Add.
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.
Set the connector’s Name and, optionally, a Description.
Click the pencil icon next to Owners to choose who can configure and manage this connector.
Click Add. The connector is created and its configuration page opens.
Find the Settings area of the page and click Edit.
Enter your PingFederate instance URL (in the form https://pingfederateserver.com) in the Instance URL field.
Paste your PingFederate username and password into the Username and Password fields.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your PingFederate connector is now pulling access data into C1. Follow these instructions to use the PingFederate 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.Resources
- GitHub repository: Access the source code, report issues, or contribute to the project.
Step 1: Set up a new PingFederate connector
In C1, navigate to Apps > Connectors and click Add connector.
Search for Baton and click Add.
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.
Set the connector’s Name and, optionally, a Description.
Click the pencil icon next to Owners to choose who can configure and manage this connector.
Click Add. The connector is created and its configuration page opens.
In the Settings area of the page, click Edit.
Click Rotate to generate a new Client ID and Secret.Carefully copy and save these credentials. We’ll use them in Step 2.
Step 2: Create Kubernetes configuration files
Create two Kubernetes manifest files for your PingFederate connector deployment:Secrets configuration
See the connector’s README or run --help to see all available configuration flags and environment variables.Deployment configuration
Step 3: Deploy the connector
Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
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 PingFederate connector to. PingFederate data should be found on the Entitlements and Accounts tabs.
Done. Your PingFederate connector is now pulling access data into C1.