TestToken validates a JWT against a specific trust’s configuration without issuing an access token. Returns per-step validation results for debugging.
Documentation Index
Fetch the complete documentation index at: https://conductorone-groman-network-requirements-updates.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
This API uses OAuth2 with the Client Credential flow. Client Credentials must be sent in the BODY, not the headers. For an example of how to implement this, refer to the c1TokenSource.Token() function.
The service principal ID (from URL path).
The trust client ID. Accepts the cutename (e.g. "clever-fox-42195") or the full client ID (e.g. "clever-fox-42195@acme.conductorone.com/wfe"). The server normalizes to the cutename portion before lookup.
The WorkloadFederationServiceTestTokenRequest message.
Successful response
The WorkloadFederationServiceTestTokenResponse message.
TestTokenStepResult represents the result of a single validation step.
TestTokenStepResult represents the result of a single validation step.
TestTokenStepResult represents the result of a single validation step.
The decoded JWT claims (best-effort, even if signature fails). Returned as JSON string for display.
TestTokenStepResult represents the result of a single validation step.
TestTokenStepResult represents the result of a single validation step.
Overall result: true only if ALL steps passed.
TestTokenStepResult represents the result of a single validation step.
TestTokenStepResult represents the result of a single validation step.