You only have to assign the user in e.g. the setup callback:
Pow.Plug.assign_current_user(conn, user, otp_app: :my_app)
danschultzer
Pow Core Team
Kurisu
@danschultzer It is me again. 
While the lock_users guide works fine, I found that the default session_controller won’t use the EnsureNotLockedUser plug when creating a new session.
Well, it is true that adding the guide plug before any route of the app will do the job, but do you recommend using it like that ?
Anyway I’m trying to use a custom session_controller but I find the process a bit complex…
Here is all I’ve read in the docs about it:
The registration and session controllers can be changed with your customized versions too, but since the routes are built on compile time, you’ll have to set them up in
router.exwith:pownamespace. For minor pre/post-processing of requests, you can use the:controller_callbacksoption. It exists to make it easier to modify flow with extensions (e.g., send a confirmation email upon user registration).
So I have a few questions.
- For custom controllers, is there a way to use the coresponding default controller view and templates?
- Is just setting up custom controllers in
router.exwith:pownamespace will be sufficient for all to work? (I seem to get some errors about view module not found…) - Is using some custom controller, means that we have to update configuration with
routes_backend: MyAppWeb.Pow.Routes? - Will it be possible to make for noobs some quick guide on a very basic custom controller ?
Thank you for your work and your time. ^^
0
danschultzer
Pow Core Team
I recommend doing that. Add it before the session routes, or add it to endpoint.ex (after the pow session plug).
Here’s the custom controllers guide: https://github.com/danschultzer/pow/blob/master/guides/CUSTOM_CONTROLLERS.md
The ideal setup is that you take full control of the flow rather than depending on Pow. Trying to hack Pow.Phoenix will become pretty complicated and obfuscate what actually goes on. I recommend just using the Pow.Plug methods/modules instead. This way you’ll keep your code explicit and easy to understand. You won’t need the routes backend, or ensure router namespace, etc.
However, the controller callbacks can be used as an alternative if it’s only some light changes in the flow. It depends. What is it you want to change?
1
Kurisu
I was thinking about a way to prevent users from receiving password reset link if their account is locked. Since in this case they won’t be authenticated (they will only provide an email), the EnsureNotLockedUser plug won’t work here, right ?
So I will have to change a bit the reset_password extension controller.
Thank you, I will take a look at the guide. I didn’t notice it before. ^^
2
danschultzer
Pow Core Team
Good call! You are right, the plug will only work when users have authenticated. I’ll update the guide with a section on this. This can be handled with a custom controller callback, but I’ll think it through and see if there’s a more explicit way of handling it.
3
Jer7
This library is great. Even noob me managed to get it up and working on my project with little trouble. I do have a dumb question though.
I am trying to change the user_id_field from :email to a custom field in the DB (:staffid) I have the schema and everything set up properly and I can access the data from that field through the Pow.Plug. I keep seeing in the readme that the user_id_field can be changed in the config, I just can’t figure out where exactly to do that.
Any help would be very much appreciated!
0
danschultzer
Pow Core Team
That’s great!
You can set the :user_id_field in your user schema module as option to the use Pow.Ecto.Schema macro:
defmodule MyApp.Users.User do
use Ecto.Schema
use Pow.Ecto.Schema,
user_id_field: :staffid
# ...
end
The :staffid column should have unique index in the db. Just to be clear since it sounds like an belongs to association field 
2
Jer7
Kurisu
I’m just a bit curious. ^^
Is it possible (or could it be) to pass a list of fields to :user_id_field, so that user can authenticate through the field of their choice?
defmodule MyApp.Users.User do
use Ecto.Schema
use Pow.Ecto.Schema,
user_id_field: [:email, :pseudo, :phone]
# ...
end
1