v0.4.6
The callback flow has been changed so sessions are now stored in the backend cache with PowAssent.Store.SessionCache instead of using Plug.Session. This prevents exposure of sensitive data, as the only thing stored in the Plug session is a random UUID.
Updated Pow requirement to ~> 1.0.17. #141
Enhancements
- [
PowAssent.Plug] AddedPowAssent.Plug.change_user/4#118 - [
PowAssent.Operations] AddedPowAssent.Operations.user_identity_changeset/4#118 - [
PowAssent.Phoenix.AuthorizationController] Now prevents user enumeration attack usingPowEmailConfirmation.Phoenix.ControllerCallbackswhenPowEmailConfirmationextension is enabled #128 - [
PowAssent.Phoenix.AuthorizationController] Now stores:changesetin session when redirecting to:add_user_idpage #137 - [
PowAssent.Phoenix.RegistrationController] Now prevents user enumeration attack usingPowEmailConfirmation.Phoenix.ControllerCallbackswhenPowEmailConfirmationextension is enabled #128 - [
PowAssent.Phoenix.RegistrationController] Now uses:changesetstored in the session when rendering:add_user_idpage #137 - [
PowAssent.Plug] Moved business logic away fromPowAssent.Phoenix.AuthorizationControllerintoPowAssent.Plug.callback_upsert/4that will authenticate, upsert user identity, or create user #133 - [
PowAssent.Store.SessionCache] Added session store module #135 - [
PowAssent.Plug] AddedPowAssent.Plug.init_session/1#135 - [
PowAssent.Plug] AddedPowAssent.Plug.put_session/3#135 - [
PowAssent.Plug] AddedPowAssent.Plug.delete_session/2#135
Bug fixes
- [
PowAssent.Ecto.Schema] Fixed issue inPowAssent.Ecto.Schema.changeset/2where confirmation token was not set thus allowing users with unconfirmed email to sign in #121
Documentation
- Added legacy migration guide #129
- Added API guide #143