I mean… I have a navbar with a logout button that still point to sessioncontroller delete. Not sure if that matter. I’m going to try your suggestion.
Oh… I think I know what’s happening:
I’m using error_handler: Pow.Phoenix.PlugErrorHandler
Ah that’s the problem. I wanted to be lazy but turns out it was bad to be lazy. Thanks!
Thanks for this library, we’ve been using it instead of Coherence for our new projects!
Is there an easy way to store sessions in the database with Ecto? The 2 provided solution “ets” and “mnesia” shows how to implement a backend for session but it’s not as simple as a “user_id” → “token” in the database. There is a concept of “keys” per user, invalidators…
Did someone already implemented this?
Thanks!
Yup, the guide shows how to set up the proper error handler since the default error handler assumes you don’t have custom routes 
Sorry for the late response, I’ve been swamped!
I haven’t seen anyone implementing this. You should note that the store backends works as key-value cache stores, so there is no concept of relational structure or assumption of user association.
However, you should be able to set up an ecto schema with user association for it since since currently the cache store is used for session ids, reset password tokens and persistent session tokens. It would be safe for future releases if you just do some basic pattern matching.
You would need a way to invalidate the keys. I think the GenServer setup in the Mnesia cache works well for that. Since you would leverage the DB you just need to have namespace, key, user association and TTL, and a unique index on the namespace-key columns.
You can build from the Mnesia cache module. You would only have to change the table_get/2, table_update/4, table_delete/2 and table_keys/2 methods, and remove the mnesia logic for table initialization and namespace of keys.
I may post an example for ecto integration when I got some free time
I’m trying to figure out how to add “Login” and “Sign Up” breadcrumbs to my site. The way I do this on the rest of the site is to create a list of tuples of {name, route} in my controller actions, but I’m not sure how to do this for the Login and Sign Up routes. Any advice here?
There are several ways of doing this. I would recommend moving the logic to relevant view module.
In the below example I make the assumption that you continue to assign breadcrumbs in your other controllers as :breadcrumbs, and just want to catch the Pow registration and session controllers (untested code, from the top of my head):
defmodule MyAppWeb.LayoutView do
use MyAppWeb, :view
alias MyAppWeb.Router.Helpers, as: Routes
@spec breadcrumbs(Plug.Conn.t()) :: [{binary(), binary()}]
def breadcrumbs(%{assigns: %{breadcrumbs: breadcrumbs}}), do: breadcrumbs
def breadcrumbs(%{private: %{phoenix_controller: Pow.Phoenix.RegistrationController, phoenix_action: :new}}), do: [{"Sign up", Routes.pow_registration_path(conn, :new)}]
def breadcrumbs(%{private: %{phoenix_controller: Pow.Phoenix.SessionController, phoenix_action: :new}}), do: [{"Sign in", Routes.pow_session_path(conn, :new)}]
def breadcrumbs(_conn), do: []
end
Now you just call breadcrumbs(@conn) in your layout template (or partial) to fetch the list.
Edit: If a user inputs an invalid password the breadcrumbs in the above example will be empty. You can either change the pattern matching to handle multiple actions for the controller:
def breadcrumbs(%{private: %{phoenix_controller: Pow.Phoenix.SessionController, phoenix_action: action}}) when action in [:new, :create], do: [{"Sign in", Routes.pow_session_path(conn, :new)}]
Or you could even just use the view and template instead of controller and action:
def breacrumbs(%{private: %{phoenix_view: Pow.Phoenix.RegistrationView, phoenix_template: "new.html"}})), do: [{"Sign in", Routes.pow_session_path(conn, :new)}]
I’m working on an umbrella project that has one admin web app.
For the login page I would like to disable the default app layout (since it would show informations we don’t want guest to see) or at least use a minimalistic view layout.
When I tried to do something like
plug :put_layout, false or plug :put_layout, {AdminWeb.LayoutView, :login}
in the router.ex then pipe only the login route through it, Pow threw an error about building the template layout.
Please, is there a way to fix this, or should I write a custom session_controller ?
– more details in the case it can help –
Since it is an admin web app, to disable registration I generated the templates and add the app view_module in pow config, then add routes only to edit and delete profile.
For session routes I also added them by hand.
In other words I didn’t use Pow macro such as pow_routes() or pow_sessions()
Hello Dan,
I want to migrate a project from coherence to pow, for that purpose I tried out your library in a new dummy project.
First I want to ask if multiple user support is still available in the latest versions?
I couldn’t get it to work following your instructions in the guide above and your comments in some github issues. Whenever I access one of the scopes it always tries to log the user from the last plug in the endpoint (Pow.Plug.Session) and that user is assigned to both current user keys (current_user and current_admin).
Also the command for generating templates and views with namespaces didn’t work properly as it didn’t use the namespace names in generating the locations of the files. The dummy project is available at the link below, in it we created the namespace folder names manually.
Thank you!
That looks like an issue with Phoenix rather than Pow. How does your routes and pipeline look? And what was the exact error thrown? It should be something like:
pipeline :admin_layout do
plug :put_layout, {AdminWeb.LayoutView, :login}
end
scope "/" do
pipe_through [:browser, :admin_layout]
pow_session_routes() # Or the custom route setup you have written
end
Yes, but the PR you’ve looked at was closed since I didn’t like the approach. What I would recommend is to set up an umbrella app with two separate web apps that each has their own Pow setup.
It’s possible to run Pow with two different user schemas in the same web app too, but all the work lies on the shoulders of the developer.
If you go down that route (I strongly recommend just separating the context with an umbrella app, or instead have user roles), then you would need to set up both routes and endpoint to handle multiple contexts, as well as some handling of routes.
Something like this (untested):
# endpoint.ex
plug Plug.Session,
otp_app: :my_app,
user: MyApp.Admins.Admin,
current_user_assigns_key: :current_admin,
session_key: "admin_auth",
session_store: {Pow.Store.CredentialsCache, ttl: :timer.minutes(30), namespace: "admin_credentials"},
routes_backend: MyAppWeb.AdminPowRoutes
plug Plug.Session, otp_app: :my_app
# router.ex
pipeline :admin do
plug Pow.Plug.Session,
user: MyApp.Admins.Admin,
current_user_assigns_key: :current_admin,
session_key: "admin_auth",
session_store: {Pow.Store.CredentialsCache, ttl: :timer.minutes(30), namespace: "admin_credentials"},
routes_backend: MyAppWeb.AdminPowRoutes
end
scope "/admin", as: "admin" do
pipe_through [:browser, :admin]
pow_routes()
end
scope "/" do
pipe_through :browser
pow_routes()
end
# admin_pow_routes.ex
defmodule MyAppWeb.AdminPowRoutes do
use Pow.Phoenix.Routes
alias MyAppWeb.Router.Helpers, as: Routes
def url_for(conn, verb, vars \\ [], query_params \\ []) do
plug = admin_namespace(plug)
Pow.Phoenix.Routes.url_for(conn, plug, verb, vars, query_params)
end
def path_for(conn, plug, verb, vars \\ [], query_params \\ []) do
plug = admin_namespace(plug)
Pow.Phoenix.Routes.path_for(conn, plug, verb, vars, query_params)
end
defp admin_namespace(plug) do
[web_module | rest] = Module.split(plug)
Module.concat([web_module, "Admin"] ++ rest)
end
end
You can take a look at the thought process I went through when I was working on this in the #24 #53 and #56 issues.