Capabilities
| Resource | Sync | Provision |
|---|---|---|
| Tenants | ||
| Users | ||
| Permissions | ||
| Roles | ||
| Groups |
Gather Frontegg credentials
Sign in to the Frontegg Portal and open
the environment you want to connect.
Copy the vendor Client ID and Client secret for the environment.
The connector uses these to mint a short-lived management JWT.
Synced resource types
- Tenants: Frontegg accounts in the environment.
- Users: Environment-wide users, including per-tenant role assignments.
- Permissions: Environment-global permission definitions.
- Roles: Per-tenant roles; resource IDs encode tenant and role.
- Groups: Per-tenant groups; resource IDs encode tenant and group.
- User membership in tenants
- Direct role assignments to users
- Group membership
- Role assignments inherited through group membership
Configure the Frontegg connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your Frontegg connector is now pulling access data into C1.
Enter the Frontegg credentials:
- Frontegg Base URL: The regional API gateway for your environment, for example
https://api.us.frontegg.com. - Frontegg Client ID: The vendor client ID from Keys & domains.
- Frontegg Client Secret: The vendor secret paired with the client ID.
Connector configuration reference
| Setting | Environment variable | Required | Description |
|---|---|---|---|
| Frontegg Base URL | BATON_BASE_URL | Yes | Regional Frontegg API gateway origin, without a trailing slash. Must match the region where vendor credentials were issued. |
| Frontegg Client ID | BATON_FRONTEGG_CLIENT_ID | Yes | Vendor client ID from Portal > Environment > Keys & domains. |
| Frontegg Client Secret | BATON_FRONTEGG_CLIENT_SECRET | Yes | Vendor secret paired with the client ID. Stored as a secret. |