-
Notifications
You must be signed in to change notification settings - Fork 156
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
Implement oauth state attribute #15
Conversation
This would indeed cover various cases of using the |
Implement oauth state attribute
Hi @doapp-ryanp, thanks a lot for your contribute. Much more appreciated. I would love to ask two more thing:
|
No - thank you for the work on this wonderful plugin. Yea man np on the other stuff. Will get to it in the next day or so. Question regarding this pull. I left the |
I should absolutly think more about this. Actually I'm not sure about keeping |
My opinion would be to remove the default all together. Most oAuth2 providers (all that I have seen) have it as an optional param. It should be used, but oauth-ng defaulting it may give developers the idea that the CRSF issue has been handled for them, which is a false (and potentially dangerous) assumption. |
I agree. If you have any time to take it off, would be great. One question, to eventually move in one different issue. How are you handling the expired token? In a new app I'm creating these days, I move the user to a specific page where I place a |
Yea I'll remove when I doc and testcase. Re your other question - its a good one - so I started a new issue here: #17 |
Pull request here #18 I can't figure out how to run your test cases - please checkout my comment in the pull request |
use state attr if defined, otherwise default to current location. QS params were also not encoded.