feat: add OAuth2 protected resource metadata endpoint for RFC 9728 #18643
+223
−0
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 OAuth2 Protected Resource Metadata Endpoint
This PR implements the OAuth2 Protected Resource Metadata endpoint according to RFC 9728. The endpoint is available at
/.well-known/oauth-protected-resource
and provides information about Coder as an OAuth2 protected resource.Key changes:
/.well-known/oauth-protected-resource
that returns metadata about Coder as an OAuth2 protected resourceOAuth2ProtectedResourceMetadata
struct in the SDKThe implementation currently returns basic metadata including the resource identifier and authorization server URL. The
scopes_supported
field is empty until a scope system based on RBAC permissions is implemented. Thebearer_methods_supported
field is omitted as Coder uses custom authentication methods rather than standard RFC 6750 bearer tokens.A TODO has been added to implement RFC 6750 bearer token support in the future.