-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
Better Docs #61
Comments
I just saw this and wanted to let you know that I would be very happy to help, if that would be useful. |
Maybe you can use ChatGPT to generate that! 😄 |
hi @sergiodxa I would love to contribute and work on a new documentation website. Can i create a PR? P.S: Seems like the |
🙏 please 🙂 It's still not clear to me what I'm supposed to use the second arg to the oauth2 strategy constructor ( I didn't even know there was an "authorizer" part of this package until I poked around in the source. How do I use that? Where are rules configured? Why is the session It may be another issue - but what if I want to store separate cookies for each token and the user info in cases where that information won't fit in just one? |
The authorized is undocumented on purpose, it's not considered stable |
I'm not sure what you mean by this, but the session ID is generated by the session storage object, not by Remix Auth, I think if you use createCookieSessionStorage there's no session ID, but that's an implementation detail that belongs to Remix. |
The name came from Passport, the idea is that you use what the strategy gives you (form strategy gives your a formData but OAuth2 based ones gives you more things) and then verify if the user exists in your app, e.g. query your DB, if you don't need to do this you can just return what the strategy gives you. |
This is outside the scope of Remix Auth, you can remove the |
Got it. In my case I'm hitting my aws cognito authorization endpoint. I get back tokens (id, access, refresh) but no user information. In the Thanks for the clarity 🙂 |
Thanks. I was comparing what I was returning from the |
The text was updated successfully, but these errors were encountered: