OAuth 2 artefact binding #149
Open
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
tplooker
force-pushed
the
tl/issue-114
branch
from
72e3522 to
12d5819
Compare
tplooker
commented
Sep 9, 2025
paulbastian
reviewed
Sep 14, 2025
paulbastian
reviewed
Sep 14, 2025
|
I think it would make sense to reference the refresh token description that is given above this section as an example? |
Co-authored-by: Paul Bastian <[email protected]>
tplooker
commented
Sep 15, 2025
jogu
reviewed
Sep 19, 2025
Co-authored-by: Joseph Heenan <[email protected]>
This was referenced Oct 24, 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.
Closes #56
Fixes #114
Looking for feedback on the approach here @panva.
I've opted to not require this behaviour via RECOMMENDED over a MUST this also makes it forward compatible with future OAuth2 extensions that might define new protocol artefacts.