Mock an OpenID Connect discovery document
A GET mock at /.well-known/openid-configuration with issuer, authorization_endpoint, token_endpoint, and jwks_uri.
Stands in for a third-party API endpoint.
Response payload
{
"issuer": "https://quickmock.dev/m/YOUR-SLUG",
"authorization_endpoint": "https://quickmock.dev/m/YOUR-SLUG/authorize",
"token_endpoint": "https://quickmock.dev/m/YOUR-SLUG/token",
"jwks_uri": "https://quickmock.dev/m/YOUR-SLUG/.well-known/jwks.json",
"response_types_supported": [
"code"
],
"subject_types_supported": [
"public"
],
"id_token_signing_alg_values_supported": [
"RS256"
]
}
Fields worth knowing
| Field | What it means |
|---|---|
| issuer | The issuer URL clients compare against a token's iss claim; it must exactly match the base URL. |
| authorization_endpoint | Where a client sends the user to log in. |
| token_endpoint | Where a client exchanges a code for tokens. |
| jwks_uri | Where a client fetches the public keys — pairs with the jwks-endpoint template. |
Create the mock
curl -X POST https://quickmock.dev/api/mocks \
-H 'Content-Type: application/json' \
-d '{
"method": "GET",
"response_status": 200,
"content_type": "application/json",
"path_suffix": ".well-known/openid-configuration",
"response_body": "{\"issuer\":\"https://quickmock.dev/m/YOUR-SLUG\",\"authorization_endpoint\":\"https://quickmock.dev/m/YOUR-SLUG/authorize\",\"token_endpoint\":\"https://quickmock.dev/m/YOUR-SLUG/token\",\"jwks_uri\":\"https://quickmock.dev/m/YOUR-SLUG/.well-known/jwks.json\",\"response_types_supported\":[\"code\"],\"subject_types_supported\":[\"public\"],\"id_token_signing_alg_values_supported\":[\"RS256\"]}"
}'
Call it
curl https://quickmock.dev/m/<slug>/.well-known/openid-configuration
What you get
GET /m/<slug>/.well-known/openid-configuration -> 200 an OIDC discovery document
replace YOUR-SLUG with the mock's real slug before using it
How this differs from the real thing
Every URL in this document is a placeholder built from YOUR-SLUG — replace it with the mock's real https://quickmock.dev/m/<slug> URL before pointing a real OIDC client at it. Editing the response body needs the admin token from the create banner; see /guide/manage-mocks-from-any-device for how that works.
Ready to use it?
Pairs well with this guide: Mock a REST API endpoint