Capabilities
Configuring the connector requires you to pass in credentials generated in Formal. Gather these credentials before you move on.
A user with the Connector Administrator or Super Administrator role in C1 and the ability to generate API keys in Formal must perform this task.
Sign into Formal and click the API Keys tile.
Give the new key a name, such as “C1 integration”.
Click Create. The new API key is generated.
Carefully and copy and save the API key.
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in C1
- Access to the set of Formal 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 Formal 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.
Paste the API key into the API key field.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Follow these instructions to use the Formal 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.
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 Formal 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 Formal connector to. Formal data should be found on the Entitlements and Accounts tabs.
