This page is the per-provider supplement to the IDP overview. Read that first.Documentation Index
Fetch the complete documentation index at: https://docs.alterauth.com/llms.txt
Use this file to discover all available pages before exploring further.
1. JWT verification
In the Clerk Dashboard:- Note the instance URL:
https://<app>.clerk.accounts.dev(development) orhttps://clerk.<custom-domain>(production with a custom domain). This is the issuer. - Decide which JWT template to send to Alter. Clerk’s session token works out of the box.
- Click Add Identity Provider.
- Paste the issuer URL, click Discover. Alter recognizes Clerk and pre-fills the claim mappings.
- The default
subclaim is Clerk’s user ID; that’s what Alter keys user records on. - For Clerk organizations with group-based authorization, set the group claim to
org_memberships(or whatever the JWT template uses) before any user signs in. - Click Add Provider.
2. OIDC sign-in (optional)
Required only forvault.authenticate() or the Wallet sign-in flow. Requires a production Clerk instance.
In the Clerk Dashboard:
- Configure → OAuth Applications → Create OAuth Application.
- Add both redirect URIs from the Alter portal as allowed callbacks.
- Copy Client ID and Client Secret.
- Open the User Authentication (OIDC) section.
- Paste credentials and Save.
3. Webhook deprovisioning (optional)
Clerk’s flow is reversed from Auth0: create the endpoint in Clerk first, then paste its signing secret into Alter. In the Alter portal → Identity page → Webhooks section:- Note the Webhook URL shown for the app. Do not click Enable yet — Clerk needs the URL first.
- Webhooks → Add Endpoint → paste the Alter webhook URL.
- Subscribe to:
user.updateduser.deletedorganizationMembership.deleted
- Copy the displayed Signing Secret (
whsec_...).
- Toggle Enable Webhooks and paste the signing secret.
- Click Save Secret.
Test
- Sign in as a test user through Clerk → confirm the user appears in the Alter portal.
- Delete the test user in Clerk → confirm their grants are revoked in Alter.
Common pitfalls
- Development vs production instance. OIDC sign-in requires production. JWT verification works in either, but issuer URLs differ.
- Custom JWT template. With a non-default JWT template, ensure the
subclaim still carries the user ID Alter should key on. Override the user-ID claim mapping in the portal if needed (only before first sign-in).
See also
- IDP overview
- JWT identity — runtime pattern.