OAuth2 authorization server metadata (RFC 8414).
GET
/.well-known/oauth-authorization-server
const url = 'https://api.siteqwality.com/.well-known/oauth-authorization-server';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.siteqwality.com/.well-known/oauth-authorization-serverResponses
Section titled “ Responses ”Authorization server metadata
Media type application/json
RFC 8414 authorization server metadata, served at
/.well-known/oauth-authorization-server so client libraries can
auto-configure instead of being handed a URL to paste.
object
issuer
required
string
token_endpoint
required
string
grant_types_supported
required
Array<string>
token_endpoint_auth_methods_supported
required
Array<string>
scopes_supported
required
Array<string>
response_types_supported
required
Empty: this server issues no authorization codes and no tokens by redirect. RFC 8414 still expects the key to be present.
Array<string>
Example generated
{ "issuer": "example", "token_endpoint": "example", "grant_types_supported": [ "example" ], "token_endpoint_auth_methods_supported": [ "example" ], "scopes_supported": [ "example" ], "response_types_supported": [ "example" ]}