Closed morgz closed 4 years ago
PowAssent currently doesn't support it. In Pow the :request_path
is handled in the URL's generated which makes it pretty easy to manage. For PowAssent it'll have to be stored in the session as the users get redirected to the provider. What complicates it further is that when the user returns multiple things can happen, and they may have an additional step before being send back to the :request_path
.
When I have some free time, I'll check what is needed to add support for this.
Thanks for the reply. When you say session, are you referring to a cookie or an entry in Mnesia / ETS?
When you say session, are you referring to a cookie or an entry in Mnesia / ETS?
The Plug session in Phoenix that may be either cookie (default and signed) or ETS. Not to be confused with auth sessions in Pow.
Added a PR to fix this in #110. You can try it out with {:pow_assent, github: "pow-auth/pow_assent", ref: "request-path"}
. Let me know if it works as expected for you 😄
Dan - you're brilliant. I've tested this and this works a treat for me. 👍
FYI v0.4.5
has been released with this fix 🚀
Using vanilla email/password pow, after successful auth, the user is redirected to their original request path. My initial testing with pow_assent, does not redirect me to my original request path.
Is this functionality not present or am I missing something?
Thanks
Dan
From defmodule Pow.Phoenix.Routes