-
Notifications
You must be signed in to change notification settings - Fork 904
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
FR: Authorization flow with PKCE #5935
Comments
Tracked internally with b/216852386. |
Any updates on this? |
Hi, thanks for filing this issue! We are unable to promise any timeline for this feature request, but adding a +1 to this will help us prioritize it on our roadmap. |
Any updates on the feature request? Does this mean the methods mentioned in the docs https://firebase.google.com/docs/auth/web/microsoft-oauth would not work? I'm coming from https://stackoverflow.com/questions/76727538/firebase-authentication-with-microsoft-error-proof-key-for-code-exchange-is-re/76815902#76815902 |
Just inspected the call to |
I did find that firebase/auth does allow you to set custom parameters with: const provider = new OAuthProvider('microsoft.com');
provider.setCustomParameters({
code_challenge: '...',
}); But not sure what to set it to yet, will read more on the pkce RFC docs |
@kdawgwilk you can generate a code challenge with |
any update ? |
Recommended best practice for browser apps is authorization code flow with PKCE.
https://datatracker.ietf.org/doc/html/draft-ietf-oauth-browser-based-apps
Are there plans to build this into the Firebase auth library?
The text was updated successfully, but these errors were encountered: