Discovery

RFC 8414 metadata, plus the auth.md `agent_auth` block

Where the authorization, token, registration and revocation endpoints are, which grant types and PKCE methods are supported, and the one scope this server issues. An agent that reads this needs nothing else to run the OAuth flow.

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

Request

  • Base URL: https://youspot.com
  • URL: https://youspot.com/.well-known/oauth-authorization-server
  • Auth: none required

Headers

If-None-Matchstring

The ETag from an earlier answer. When it still matches, the answer is 304 Not Modified with no body.

Response

The metadata.

issuerstring uri required
authorization_endpointstring uri required
token_endpointstring uri required
registration_endpointstring uri
revocation_endpointstring uri
scopes_supportedstring[]
response_types_supportedstring[]
grant_types_supportedstring[]
code_challenge_methods_supportedstring[]

S256 only. plain is refused.

token_endpoint_auth_methods_supportedstring[]
service_documentationstring uri
agent_authobject

What an agent can hold here, and how to get it. Mirrors /auth.md.

Changes

No recorded changes to this operation across all 1 revision of this API.