feat(oauth): Add Authorization Server Metadata endpoint (RFC 8414) #107017
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add /.well-known/oauth-authorization-server discovery endpoint that returns JSON metadata describing the OAuth authorization server's configuration. This allows clients to automatically discover supported grant types, PKCE methods, authentication methods, and endpoint URLs. The metadata includes: - Issuer identifier and all OAuth endpoint URLs - Supported grant types (authorization_code, refresh_token, device_code) - PKCE support (S256 only) - Client authentication methods - Available scopes Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
bot
added
the
Scope: Backend
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add
/.well-known/oauth-authorization-serverdiscovery endpoint per RFC 8414 that returns JSON metadata describing the OAuth authorization server's configuration.This enables OAuth clients to automatically discover Sentry's supported capabilities without hardcoding configuration, improving interoperability and supporting OAuth 2.1 compliance.
The metadata document includes:
authorization_code,refresh_token,urn:ietf:params:oauth:grant-type:device_codeclient_secret_basic,client_secret_post,noneSENTRY_SCOPESResponse is cached for 1 hour with public cache headers.
Refs #99002