auth: support well-known paths at domain root, with prefix path, and with suffix path #459
+121
−38
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.
According to the RFC 8414, if the issuer identifier value contains a path component, the well-known URI must include that path as a suffix.
For example, if the issuer identifier is
https://example.com/issuer1
, then the OAuth 2.0 Authorization Server Metadata URL should be:In practice, however, some implementations diverge from the spec and either:
This PR updates the agent to try all three variants in the following order, improving interoperability across different authorization server implementations:
Implements: #403
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context
Caveat: I'm new to Rust development. If this PR is missing something or doesn't follow best practices, please let me know. I'm happy to make any updates.