feat: add OAuth2 protected resource metadata endpoint for RFC 9728 #18643
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
This was referenced Jun 27, 2025
5be6c6a to
fded148
Compare
1e2bc51 to
3de973b
Compare
3de973b to
9f159b0
Compare
9b7f5d9 to
7ef25b1
Compare
47d9a0a to
bffc160
Compare
7ef25b1 to
f0608bc
Compare
bffc160 to
e733c7b
Compare
c68a923 to
f55771a
Compare
e733c7b to
70e8be9
Compare
f55771a to
34af681
Compare
70e8be9 to
476c079
Compare
34af681 to
e72476e
Compare
476c079 to
d2eb876
Compare
Emyrk
approved these changes
Jul 1, 2025
1858134 to
a239eaa
Compare
2621adf to
661c0e6
Compare
a239eaa to
4ca3595
Compare
661c0e6 to
5be06e7
Compare
4ca3595 to
23374cd
Compare
5be06e7 to
3275584
Compare
43fcceb to
db5e215
Compare
3275584 to
9bd7ff5
Compare
db5e215 to
953036f
Compare
9bd7ff5 to
1d7dbb1
Compare
1d7dbb1 to
7cab8d5
Compare
953036f to
22c2dc6
Compare
a1cb748 to
1809030
Compare
22c2dc6 to
14e6e22
Compare
1809030 to
910d2c8
Compare
14e6e22 to
5791cb0
Compare
5791cb0 to
7e0ce8a
Compare
910d2c8 to
1b73b1a
Compare
- Add OAuth2ProtectedResourceMetadata struct in codersdk/oauth2.go - Implement /.well-known/oauth-protected-resource endpoint handler - Register route in coderd.go for Protected Resource Metadata discovery - Add comprehensive test coverage in oauth2_metadata_test.go - Update OpenAPI documentation and generated API types - Correctly omit bearer_methods_supported field (Coder uses custom auth) - Support MCP OAuth2 compliance requirement for resource server metadata This implements RFC 9728 OAuth 2.0 Protected Resource Metadata to enable MCP clients to discover resource server capabilities and authorization servers. Change-Id: I089232ae755acf13eb0a7be46944c9eeaaafb75b Signed-off-by: Thomas Kosiewski <[email protected]>
7e0ce8a to
59b7a9d
Compare
Merge activity
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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-resourceand provides information about Coder as an OAuth2 protected resource.Key changes:
/.well-known/oauth-protected-resourcethat returns metadata about Coder as an OAuth2 protected resourceOAuth2ProtectedResourceMetadatastruct in the SDKThe implementation currently returns basic metadata including the resource identifier and authorization server URL. The
scopes_supportedfield is empty until a scope system based on RBAC permissions is implemented. Thebearer_methods_supportedfield 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.