Compliance ConnectorsSetup by categoryIdentity & SSO
Frontegg
Connect Frontegg to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Frontegg connection as identity & sso evidence. Automated collection is not available for this provider yet.
| Category | Identity & SSO |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Frontegg:
- In the Frontegg Portal, open your environment and go to Keys & domains.
- Copy the environment's Client ID and API Key.
- Exchange them for a vendor token: POST {"clientId": "<Client ID>", "secret": "<API Key>"} to the /auth/vendor/ endpoint for your region (EU https://api.frontegg.com/auth/vendor/, US https://api.us.frontegg.com/auth/vendor/, CA https://api.ca.frontegg.com/auth/vendor/, AU https://api.au.frontegg.com/auth/vendor/).
- Paste the returned token into Safeguard.
Where to find the other values:
- Base URL (optional): The regional Frontegg API base for your environment: https://api.frontegg.com (EU), https://api.us.frontegg.com (US), https://api.ca.frontegg.com (CA) or https://api.au.frontegg.com (AU).
Frontegg issues this credential through its API or its support team, not through its admin screens.
Source: developers.frontegg.com, developers.frontegg.com, checked 2026-10-07.
-
On Compliance › Connectors, open Frontegg, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
No automated compliance test reads Frontegg yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- Identity & SSO connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks