OpenID Connect
Clowk OpenID Connect discovery endpoint at /.well-known/openid-configuration, with the OAuth authorization code flow, provider scopes and HS256 tokens.
GET /.well-known/openid-configuration
Clowk exposes a basic OpenID Connect discovery endpoint. This allows OIDC-compatible tools to discover Clowk's authentication endpoints automatically.
Request
curl https://myapp.clowk.dev/.well-known/openid-configurationNo authentication is required.
Response
{
"issuer": "https://myapp.clowk.dev",
"authorization_endpoint": "https://myapp.clowk.dev/oauth/authorize",
"token_endpoint": "https://myapp.clowk.dev/api/v1/tokens/verify",
"userinfo_endpoint": "https://myapp.clowk.dev/api/v1/users",
"response_types_supported": ["code"],
"subject_types_supported": ["public"],
"id_token_signing_alg_values_supported": ["HS256"]
}| Field | Description |
|---|---|
issuer | The Clowk base URL |
authorization_endpoint | Where to start the OAuth flow |
token_endpoint | Where to verify tokens |
userinfo_endpoint | Where to fetch user data |
response_types_supported | Only authorization code flow is supported |
id_token_signing_alg_values_supported | Tokens are signed with HS256 |
OAuth flow
Clowk uses the authorization code flow:
- Redirect the user to
/oauth/authorizewith aproviderandredirect_uri - Clowk handles the OAuth dance with the provider (Google, GitHub, Twitter)
- On success, Clowk redirects back to your
redirect_uriwith atokenquery parameter - Verify the token with
POST /api/v1/tokens/verifyor decode it locally using your secret key
GET /oauth/authorize?provider=google&redirect_uri=https://app.example.com/auth/callbackSupported providers
| Provider | Scopes |
|---|---|
openid, email, profile | |
| GitHub | user:email, read:user |
tweet.read, users.read, offline.access |
State parameter
Each OAuth request generates a unique state value to prevent CSRF attacks. The state token expires after 10 minutes. Twitter flows also use PKCE (code challenge and verifier).
Search Operators
Reference for the Clowk search query language used by the users and sessions search API: exact match, wildcards, negation, OR and date comparisons.
How it works
How Clowk authentication works, from redirect to signed JWT: the broker model, OAuth providers, custom credentials, token delivery and verification.