-
-
Notifications
You must be signed in to change notification settings - Fork 932
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
req.user not available in grant flow #120
Comments
Yeah this makes sense, I think we could just add an extra step before |
Why not just add that to |
Yep, that could make even better sense! Happy to review a PR on this :) |
I'll get on it |
I'd like to change the way this is implemented, I haven't yet released the commit that fixed it but, to keep with convention, client will now be accessible See: #143 |
Closes oauthjs#120 Closes oauthjs#124 Closes oauthjs#132
I'd like to generate tokens using encryption/decryption - as briefly mentioned in https://auth0.com/blog/2014/01/27/ten-things-you-should-know-about-tokens-and-cookies/#token-oauth (points 8 & 9).
Thus removing the need to persist tokens.
For that I need to access the user and client info in the model.generateToken , but req.user is only available in the authorise flow and not while granting.
Also - req.client is already used by express.js.
Thanks
The text was updated successfully, but these errors were encountered: