Resource Indicators for OAuth 2.0 (RFC 8707) #26
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
jozefizso
requested changes
Jun 30, 2025
DominikPalo
force-pushed
the
feature/22-resource-indicators-for-oauth-20-rfc-8707
branch
from
f9adad8 to
aa903d1
Compare
According to RFC 8707: The resource parameter can carry the location of a protected resource, typically as an https URL or a more abstract identifier.
DominikPalo
force-pushed
the
feature/22-resource-indicators-for-oauth-20-rfc-8707
branch
from
7305448 to
8303170
Compare
m-kovac
approved these changes
Jul 1, 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.
This PR adds support for setting resource indicators according to the specification in RFC 8707.
It is partially based on a previous Slido-specific implementation, but to fully align with the RFC, we need to be able to set multiple resource indicators when requesting a token: