I’m working on an application that uses Pow for user authentication. One of the features I need to implement is to invite users, but this is done by a non-interactive process. Users will still verify themselves via the same process. I’m a bit lost in the documentation, but from what I see, I can …

You can exclude PowInvitation in the Pow.Extension.Phoenix.Router macro opts and add in the routes manually: defmodule MyAppWeb.Router do use MyAppWeb, :router use Pow.Phoenix.Router use Pow.Extension.Phoenix.Router, extensions: [PowResetPassword, PowEmailConfirmation] # ... scope "…

I guess I’m still stuck on the concept. All the calls for PowInvitation require a Plug.Conn to carry variables through. My use case does not use a Conn, so I feel like I’m trying to reimplement all the methods to get this to work. Am I making this harder than it needs to be? Update: Maybe I’ve …

[image] NullOranje: I create a dummy Conn and use `Pow.Plug.put_config(conn, config) to store Yeah, this is the easiest. It’s also how you deal with absinthe where you don’t have access to conn: Use Pow.PasswordReset.Plug.create_reset_token without a conn · Issue #61 · pow-auth/pow · GitHub I…

At least I’m not crazy. It still feels a bit wrong, but it does work well, so I guess that’s what matters. Thanks!

One last question: I’ve customized the user registration template for Pow, but PowInvitaiton wants to use it’s own. I’d like to use the same template for both. I’m still new to Phoenix, so I’m having a hard time figuring out how to have the PowInvitation controller use my custom view/template.

If you’ve set the :web_module in the Pow config, then the extensions will also use custom templates. The PowInvitation templates are generated with mix pow.extension.phoenix.gen.templates --extension PowInvitation, and you should have seen an error if they where not generated visiting the invitation…

RIght, but it’s a separate template for PowInvitation. I’d rather not duplicate myself with two sets of templates for users to set their passwords. Is it possible for the modules to share the same username/password template?

Set up a partial template in Phoenix, and use that in both: # pow/registration/new.html.eex <%= render "_form.html", changeset: @changeset, action: @action %> # pow_invitation/invitation/new.html.eex <%= render MyAppWeb.Pow.RegistrationView, "_form.html", changeset: @changeset, action: @action %>…

Hey Dan, I followed your steps to create a custom invite and called PowInvitation.Ecto.Context.create(invited_by, params, config) like you suggested, then passed the user to the deliver_email function like you suggested. But user.invitation_token is the unsigned UUID. So the emails were going out w…

I needed to display the invitation link in the app for admin users. This here worked perfectly. Thank you. [image] MyNameIsURL: token = PowInvitation.Plug.sign_invitation_token(conn, %{ invitation_token: user.invitation_token }) url = Routes.pow_invitation_invitation_path(conn…

Elixir Programming Language Forum

Customize PowInvitation?

Questions & Help Questions

NullOranje January 24, 2020, 2:09pm 3

That’s exactly what I was looking to do.. Thanks @danschultzer!