PowEmailConfirmation does not kick in

hrishikeshchoudhari

I am using Pow on a blank Phoenix project, with all 4 extensions installed.

When a new user is registered, it is automatically signed in, and the session is set, without waiting for the email confirmation.

Phoenix v1.5.3 (project generated with --live)
Pow v1.0.20

In Feb 2020, I had tried this once, with only the PowEmailConfirmation extension, and it was working as expected.

I inspected every line, and it is per the documentation here - PowEmailConfirmation — Pow v1.0.39

Any help?

My router.ex:

defmodule LiveblogWeb.Router do
  use LiveblogWeb, :router
  use Pow.Phoenix.Router
  use Pow.Extension.Phoenix.Router,
    extensions: [PowEmailConfirmation, PowInvitation, PowPersistentSession, PowResetPassword]

  pipeline :browser do
    plug :accepts, ["html"]
    plug :fetch_session
    plug :fetch_live_flash
    plug :put_root_layout, {LiveblogWeb.LayoutView, :root}
    plug :protect_from_forgery
    plug :put_secure_browser_headers
  end

  pipeline :api do
    plug :accepts, ["json"]
  end

  pipeline :protected do
    plug Pow.Plug.RequireAuthenticated,
      error_handler: Pow.Phoenix.PlugErrorHandler
  end


  scope "/" do
    pipe_through :browser

    pow_routes()
    pow_extension_routes()
  end

  scope "/", LiveblogWeb do
    pipe_through [:browser, :protected]

    # live "/", PageLive, :index
    resources "/item", ItemController, except: [:index]
    # Add your protected routes here
  end

  scope "/", LiveblogWeb do
    pipe_through :browser

    resources "/", ItemController, only: [:index]
  end

Any help?

5 comments

/phoenix #pow #pow-email-confirmation

0 1099 5

2020-07-08 06:06:03 UTC

Showing Posts 1 to 5

Show Best Posts
Show All (oldest first)
Show All (newest first)

danschultzer

Pow Core Team

Check if you got this in your Pow config:

config :my_app, :pow,
  user: MyApp.Users.User,
  repo: MyApp.Repo,
  extensions: [PowEmailConfirmation, PowInvitation, PowPersistentSession, PowResetPassword],
  controller_callbacks: Pow.Extension.Phoenix.ControllerCallbacks

And this in your user module:

defmodule MyApp.Users.User do
  use Ecto.Schema
  use Pow.Ecto.Schema
  use Pow.Extension.Ecto.Schema,
    extensions: [PowEmailConfirmation, PowInvitation, PowPersistentSession, PowResetPassword]

  # ...

  def changeset(user_or_changeset, attrs) do
    user_or_changeset
    |> pow_changeset(attrs)
    |> pow_extension_changeset(attrs)
  end
end

If both of the above are correctly set then I would look at the changeset to make sure that it isn’t overriding email confirmation handling.

Post #1

hrishikeshchoudhari

Yes, both files seem correct.

My config.exs:

config :liveblog, :pow,
  user: Liveblog.Users.User,
  repo: Liveblog.Repo,
  mailer_backend: LiveblogWeb.Pow.Mailer,
  extension: [PowEmailConfirmation, PowInvitation, PowPersistentSession, PowResetPassword],
  controller_callbacks: Pow.Extension.Phoenix.ControllerCallbacks,
  web_module: LiveblogWeb,
  web_mailer_module: LiveblogWeb

config :liveblog, LiveblogWeb.Pow.Mailer,
  adapter: Swoosh.Adapters.Postmark,
  api_key: "****"

And the User module:

defmodule Liveblog.Users.User do
  use Ecto.Schema
  use Pow.Ecto.Schema
  use Pow.Extension.Ecto.Schema,
    extensions: [PowEmailConfirmation, PowInvitation, PowPersistentSession, PowResetPassword]

  schema "users" do
    pow_user_fields()

    timestamps()
  end

  def changeset(user_or_changeset, attrs) do
    user_or_changeset
    |> pow_changeset(attrs)
    |> pow_extension_changeset(attrs)
  end
end

Taken exactly as per the docs..

I would look at the changeset to make sure that it isn’t overriding email confirmation handling.

How do I do that?

Post #2

hrishikeshchoudhari

Damn! Missed the pluralization for extensions in the config.exs file! Added the missing s and it is working correctly!

Post #3

hrishikeshchoudhari

Offtopic - is there any way to catch errors like this in Elixir? Would Dialyzer help?

Post #4

danschultzer

Pow Core Team

Unfortunately not. I would have to build config validation into Pow for that to work, but not sure if it’s a good idea, or possible, as Pow extensions might also use the config. The upside is that this is usually something you would catch very early on, and only has to be fixed once.

Post #5

— All posts loaded —