Google/OAuth Passing State
I'm implementing an invite type system, where the user can join a team with an invite code. This all works with the normal password flow (I added the invite code as an argument to the action) with a custom change to read the argument, but I'm not quite sure how to get that invite code through the various redirects for google/oauth flows, so it gets added to the google registration action as an argument.
Previously in other tools and languages I've passed state back and forth through as query params on the redirect_url or state. Is there any mechanism for that with the existing strategies? I want to support both invite code and no invite codes based on the registration url.
So far, I've been able to work around this by utilizing the secrets module for building up the
However, I'm not sure now how to get that state/invite code back to the action.
Any suggestions on where to start?
Previously in other tools and languages I've passed state back and forth through as query params on the redirect_url or state. Is there any mechanism for that with the existing strategies? I want to support both invite code and no invite codes based on the registration url.
So far, I've been able to work around this by utilizing the secrets module for building up the
authorization_paramsstateHowever, I'm not sure now how to get that state/invite code back to the action.
Any suggestions on where to start?
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.
2,193Members
Resources
Similar Threads
Was this page helpful?
