feat: expose OAuth metadata discovery provenance#1043
Closed
tsarlandie-oai wants to merge 1 commit into
Closed
Conversation
github-actions
Bot
added
T-core
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
AuthorizationMetadataSourceandDiscoveredAuthorizationMetadataAuthorizationManager::discover_metadata_with_source()discover_metadata()result and legacy conformance behaviorWhy
OAuth discovery returned normalized authorization metadata without retaining where it came from. Callers therefore could not distinguish standards-based protected-resource or authorization-server discovery from the synthesized legacy fallback.
The new API exposes that provenance while leaving the existing discovery API and behavior unchanged.
Validation
Fixes #1037