-
Notifications
You must be signed in to change notification settings - Fork 18
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
Provide example with react-admin v3 using the authorization code flow and PKCE #5
Comments
That would be great, indeed 👍 |
Thank you very much for this example, but also I would appreciate, if possible, the example could also support for both standard(username/password) + OAuth. |
We are using this in our implementation of Oauth and I figured why not be a good neighbour and share. Here is my fork, I still need some help debugging the "Please Login Error" but at least the flow is working and we can get access to the token. Some of the API packages have been deprecated and/or move and the docs need some love. I'd love to help where I can if some other devs are willing to do a code review. Thanks in advance. |
I'm not sure if anyone is following this project, I was able to get OAuth working with React Admin V3. Google does not allow URL fragments (what creates the /#/ on the React Admin URL) thus createHashHistory used by default was creating a bug. This has been resolved by using createBrowserHistory. We have not needed to implement PKCE yet, however, this pull request will allow you to use the authorization_code workflow in the meantime. |
Could you please provide an example with react-admin v3 using the authorization code flow and PKCE?
Thank you.
The text was updated successfully, but these errors were encountered: