docs(oauth2): document resource indicators - #81
Merged
Conversation
RFC 8707 landed in the code with #71, #74, #76 and #77, and the user-facing documentation never followed it: main has no mention of resource indicators anywhere under docs/content. The feature is opt-in and silent, so a reader has no way to discover it exists or to learn that a client can only request resources it was registered for. The text is e39cb15 from docs/rfc8707-resource-indicators, which was written against the feature but only ever reached branches that were superseded rather than merged. Restoring it here rather than leaving it to be lost with them.
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.
RFC 8707 shipped across #71, #74, #76 and #77. The documentation did not follow it, and
mainhas no mention of resource indicators anywhere underdocs/content.That matters more than usual for this feature because it is opt-in and silent. A client that sends no
resourcegets exactly the token it always got, so nothing surfaces the capability to a reader, and nothing tells them a client may only request resources it was registered for.The text is
e39cb15, written against the feature ondocs/rfc8707-resource-indicators. That branch and its siblings were superseded rather than merged, so this section was about to be deleted along with them.Found while auditing every branch for work missing from main. Nothing else was missing.