Add consent, public clients, and refresh-token reuse detection - #4
Open
joneja09 wants to merge 1 commit into
Open
Conversation
Show a consent screen before issuing authorization codes, support public SPA clients that use PKCE without a secret, and revoke a refresh-token family if a rotated token is presented again. Co-authored-by: Jeff Jones <joneja09@users.noreply.github.com>
joneja09
marked this pull request as ready for review
August 26, 2026 14:23
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
2 participants
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.
Depends on #3.
Completes the remaining self-hosted auth work (without Duende):
/consentbefore an authorization code is issued (remembered per user + client + scopes)requireClientSecret: false) — PKCE required, no client secret, no client_credentials grant. Seeded asdemo-spaTests
dotnet test: 14 passed.