Teleport

Record your Teleport connection as identity & sso evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Teleport:

   1. Teleport API clients load credentials from a Teleport profile created by tsh login; the Profile Credentials loader retrieves them from the current profile.
   2. As a Teleport admin, create a user for the API client with tctl users add api-admin --roles=editor (the getting-started guide uses the built-in editor role).
   3. Log in as that user with tsh login --user=api-admin --proxy=<your proxy address>; the API client then loads credentials from that profile.

   Where to find the other values:

   • Base URL (optional): Your Teleport proxy address, as used in tsh login --proxy= (the guide's example is tele.example.com).

   Teleport issues this credential through its API or its support team, not through its admin screens.

   Source: goteleport.com, checked 2026-10-07.

2. On Compliance › Connectors, open Teleport, 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)	—

3. Click Connect with token.

Frameworks

No automated compliance test reads Teleport 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