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 isproject:{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.
Authorization Server Metadata object
{
"issuer": "https://auth.gigs.com",
"token_endpoint": "https://auth.gigs.com/oauth/token",
"jwks_uri": "https://auth.gigs.com/.well-known/jwks.json",
"grant_types_supported": [
"client_credentials"
],
"token_endpoint_auth_methods_supported": [
"client_secret_basic",
"private_key_jwt"
],
"token_endpoint_auth_signing_alg_values_supported": [
"RS256",
"PS256"
]
}