C1 provides identity governance for Keeper. Integrate your Keeper instance with
C1 for unified visibility and governance over team membership.
Capabilities Resource Sync Provision Users Teams
The connector reads each Keeper user, each team, and the membership of every
team through the Keeper SCIM 2.0 API.
Gather Keeper credentials You need Keeper Administrator permissions on the node you want to sync, with the
ability to configure provisioning.
Open the node’s Provisioning tab and add a SCIM provisioning method.
Keeper generates a SCIM endpoint URL and a bearer token.
Copy the bearer token . From the endpoint URL
https://<domain>/api/rest/scim/v2/<node-id>, note the domain (your
Keeper region host, for example keepersecurity.com) and the node ID
(the number at the end of the path).
Follow these instructions to use a built-in, no-code connector hosted by C1.
In C1, navigate to Integrations > Connectors and click Add connector .
Search for Keeper and click Add .
Choose how to set up the new Keeper connector.
Set the owner for this connector.
Find the Settings area of the page and click Edit .
Enter the Keeper credentials:
Keeper domain : your Keeper region host, for example keepersecurity.com.Node ID : the node identifier from the SCIM endpoint URL.SCIM token : the bearer token generated when you added SCIM provisioning.
The connector’s label changes to Syncing , followed by Connected . You can view the logs to ensure that information is syncing.
Done. Your Keeper connector is now pulling access data into C1.Follow these instructions to run the Keeper connector in your own
environment.
Create a secret for the Keeper SCIM token.
Configure the connector with your Keeper domain, node ID, and the SCIM
token secret.
Deploy the connector using your standard self-hosted connector process.
Done. Your Keeper connector is now pulling access data into C1.
