-
Notifications
You must be signed in to change notification settings - Fork 46
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.
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
Add auth extension handling #586
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: Fantix King <[email protected]>
verify_response = await self._http_request( | ||
"POST", | ||
"/verify", | ||
json={ | ||
"verification_token": verification_token, | ||
"provider": self.provider, | ||
}, | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it expected that the verification will proceed (even successfully) with or without a valid PKCE verifier?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's right. PKCE just protects the actual auth token exchange, so you can verify an email from any user agent, but you will not be able to then parlay that into an authentication unless you have the PKCE verifier.
This adds the
gel.auth
module as the general binding of the Gel auth extension.