OIDC discovery document | Crehana Developers

{
  "issuer": "string",
  "authorization_endpoint": "string",
  "token_endpoint": "string",
  "userinfo_endpoint": "string",
  "jwks_uri": "string",
  "revocation_endpoint": "string",
  "introspection_endpoint": "string",
  "scopes_supported": [
    "string"
  ],
  "response_types_supported": [
    "string"
  ],
  "grant_types_supported": [
    "string"
  ],
  "code_challenge_methods_supported": [
    "string"
  ],
  "id_token_signing_alg_values_supported": [
    "string"
  ],
  "token_endpoint_auth_methods_supported": [
    "string"
  ],
  "subject_types_supported": [
    "string"
  ],
  "registration_endpoint": "string"
}

Returns the OpenID Connect discovery metadata. The endpoint URLs already point at this API's REST routes and must not be rewritten.

Authentication

Api-Keystring

API key of the organization. Always sent together with the Secret-Access header.

Response

Successful Response

issuerstring

authorization_endpointstring

token_endpointstring

userinfo_endpointstring

jwks_uristring

revocation_endpointstring

introspection_endpointstring

scopes_supportedlist of strings

response_types_supportedlist of strings

grant_types_supportedlist of strings

code_challenge_methods_supportedlist of strings

id_token_signing_alg_values_supportedlist of strings

token_endpoint_auth_methods_supportedlist of strings

subject_types_supportedlist of strings

registration_endpointstringOptional

$	curl https://qa.creha.co/api/v5/rest/auth/oauth2/.well-known/openid-configuration \
>	-H "Secret-Access: Secret-Access" \
>	-H "Api-Key: <apiKey>"

Authentication

Headers

Response