Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add optional PKCE challenge in email verification #7037

Merged
merged 1 commit into from Mar 13, 2024
Merged

Add optional PKCE challenge in email verification #7037

merged 1 commit into from Mar 13, 2024

Commits on Mar 13, 2024

  1. Add optional PKCE challenge in email verification 

    Currently, the email verification endpoint assumes
that if you only provide the email address, you
are not in a PKCE flow, which means the
verification ends with a redirect, or no content.
However, most of the supporting libraries expect
that verification ends with a PKCE code exchange.
Adding an optional PKCE challenge to the email
verification endpoint allows the client perform
the PKCE code exchange even if they only have an
email.
    @scotttrinh
    scotttrinh committed Mar 13, 2024
    Copy the full SHA
    d9e040a View commit details
    Browse the repository at this point in the history