# Authorization Server Metadata

OAuth 2.0 Authorization Server Metadata as defined by RFC 8414.

Only the metadata that describes capabilities we actually implement is
advertised. Fields for unimplemented features are deliberately omitted
rather than populated with placeholders:

- `authorization_endpoint` — we implement no redirect-based authorization
  endpoint. RFC 8414 section 2 permits omitting it when no supported grant
  type uses it.
- `registration_endpoint` — dynamic client registration (RFC 7591) is not
  supported; clients are registered out of band.
- `revocation_endpoint` / `introspection_endpoint` — access tokens are
  self-contained JWTs that cannot be revoked and do not need introspection.
- `scopes_supported` — the scope space is `project:{project_id}`, so the
  set of valid values is per-application and cannot be enumerated here.
- `code_challenge_methods_supported` — PKCE (RFC 7636) only applies to the
  authorization code grant, which we do not support.

## Properties

| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `issuer` | string | Yes | The authorization server's issuer identifier. Matches the `iss` claim of every token we issue. When authenticating with `private_key_jwt`, this is also the value of the client assertion's `aud` claim. |
| `token_endpoint` | string | Yes | URL of the OAuth 2.0 Token Endpoint. |
| `jwks_uri` | string | Yes | URL of the JSON Web Key Set (JWKS) document containing the keys that sign our access tokens. |
| `grant_types_supported` | string[] | Yes | List of the supported OAuth 2.0 grant type values. |
| `token_endpoint_auth_methods_supported` | string[] | Yes | List of client authentication methods supported by the Token Endpoint. |
| `token_endpoint_auth_signing_alg_values_supported` | string[] | Yes | List of JWS signing algorithms supported by the Token Endpoint for the signature on the JWT used to authenticate the client at the Token Endpoint for the `private_key_jwt` authentication method. |
