C1 provides identity governance for GitGuardian. Integrate your
GitGuardian workspace with C1 for unified visibility and governance over
user access.
Capabilities Resource Sync Provision Members Teams
The connector reads one GitGuardian workspace. It syncs the workspace’s
members and teams, along with each team’s membership — including whether
each member is a team leader or a regular team member. Each member’s
workspace access level (owner, manager, member, or restricted) and
active status are carried on the member for visibility, and deactivated
members appear as disabled users.
Gather GitGuardian credentials You need a manager or owner access level on your GitGuardian workspace to
create an API token with the required scopes.
Sign in to the GitGuardian dashboard.
Go to API > Personal access tokens and click
Create token .
Give the token a descriptive name, such as ConductorOne, and
select the members:read and teams:read scopes.
Copy the token when it is shown.
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 GitGuardian and click Add .
Choose how to set up the new GitGuardian connector.
Set the owner for this connector.
Find the Settings area of the page and click Edit .
Enter the GitGuardian credentials:
API token : the token created in the API settings.
The connector’s label changes to Syncing , followed by Connected . You can view the logs to ensure that information is syncing.
Done. Your GitGuardian connector is now pulling access data into C1.Follow these instructions to run the GitGuardian connector in your own
environment.
Create a secret for the GitGuardian API token.
Configure the connector environment variables:
BATON_GITGUARDIAN_API_TOKEN : the token created in the API
settings.
Deploy the connector using your standard self-hosted connector process.
Done. Your GitGuardian connector is now pulling access data into C1.
