OAuth 2.0 Authorization Server Metadata (RFC 8414)

GET

/api/v5/rest/auth/oauth2/.well-known/oauth-authorization-server

GET

/api/v5/rest/auth/oauth2/.well-known/oauth-authorization-server

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

200Retrieved

1 {
2   "issuer": "string",
3   "authorization_endpoint": "string",
4   "token_endpoint": "string",
5   "userinfo_endpoint": "string",
6   "jwks_uri": "string",
7   "revocation_endpoint": "string",
8   "introspection_endpoint": "string",
9   "scopes_supported": [
10     "string"
11   ],
12   "response_types_supported": [
13     "string"
14   ],
15   "grant_types_supported": [
16     "string"
17   ],
18   "code_challenge_methods_supported": [
19     "string"
20   ],
21   "id_token_signing_alg_values_supported": [
22     "string"
23   ],
24   "token_endpoint_auth_methods_supported": [
25     "string"
26   ],
27   "subject_types_supported": [
28     "string"
29   ],
30   "registration_endpoint": "string"
31 }

RFC 8414 authorization server metadata. Alias of /.well-known/openid-configuration: returns the same discovery body so that OAuth-only clients that probe the RFC 8414 well-known location receive the server metadata instead of a 404.

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

Authentication

Headers

Response