Skip to content
InternetData

Discovery

get/.well-known/oauth-authorization-server

RFC 8414 authorization server metadata: the endpoints, the grant types and the scopes this server supports.

Read this rather than hardcoding endpoints. It is also served at /.well-known/openid-configuration, identically, because several clients probe that path first.

Responses

200application/json

The server's metadata.

issuerrequiredstring
authorization_endpointrequiredstring
token_endpointrequiredstring
device_authorization_endpointstring
revocation_endpointstring
scopes_supportedarray<string>
response_types_supportedarray<string>
grant_types_supportedarray<string>
code_challenge_methods_supportedarray<string>
client_id_metadata_document_supportedboolean

Any client may sign in with an https client_id serving its own metadata.

registration_endpointstring

RFC 7591 dynamic client registration, for a client that cannot serve its own metadata.

token_endpoint_auth_methods_supportedarray<string>

Always none. Every client is public and has no secret.

authorization_response_iss_parameter_supportedboolean

RFC 9207. A redirect back from the authorization endpoint carries iss.

service_documentationstring
TypeScript type
ts
{
  issuer: string;
  authorization_endpoint: string;
  token_endpoint: string;
  device_authorization_endpoint?: string;
  revocation_endpoint?: string;
  scopes_supported?: string[];
  response_types_supported?: string[];
  grant_types_supported?: string[];
  code_challenge_methods_supported?: string[];
  client_id_metadata_document_supported?: boolean;
  registration_endpoint?: string;
  token_endpoint_auth_methods_supported?: string[];
  authorization_response_iss_parameter_supported?: boolean;
  service_documentation?: string;
}