Include /.well-known/jwks in the paths covered by OpenIddict #19749
+1
−1
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
lauraneto
approved these changes
Jul 18, 2025
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.
Prerequisites
If there's an existing issue for this PR then this fixes #19652
Description
#16549 (and the subsequent #16845) causes the linked issue. In essence, the
ProcessRequestContextHandlerfrom those PRs prevents OpenIddict from handling/.well-known/jwks, ultimately leading to a 404 response.This PR fixes it by adding
/.well-known/jwksto the allow-list of paths inProcessRequestContextHandler.Testing this PR
First and foremost, verify that
/.well-known/openid-configurationstill works, and that thejwks_uriproperty in the response contains"[host]/.well-known/jwks"(it should remain unaffected by this PR).Now verify that
/.well-known/jwksalso works 👍