Exchange Auth
POST/api/auth-exchange
Exchanges an external JWT token (verified via the organization's configured JWKS URI) for Webrix Connect credentials.
This endpoint enables programmatic token generation for users authenticated by your identity provider (Okta, Keycloak, etc.).
Prerequisites
- Configure your SSO provider (Okta or Keycloak) in Admin Settings with a JWKS URI
- Generate an API token with the
connect:exchange-authscope (orconnect:write/allwhich include it)
How it works
- Your application authenticates a user with your identity provider and obtains a JWT
- Send the JWT in the
Authorization: Bearer <jwt>header along with your API key in thex-api-keyheader - Webrix verifies the JWT against the configured JWKS URI
- If valid, Webrix issues Connect credentials (access token, refresh token, etc.) with the original JWT stored as the
id_token
The JWT must contain a sub, email, or client_id claim to identify the user.
Request
Responses
- 200
- 400
- 401
- 403
- 500
JWT verified and credentials issued successfully
Bad request (empty JWT, missing claims, or JWKS URI not configured)
Missing or invalid Authorization header or API key
API key does not have the required scope
Internal server error