Setting the :password_hash
to nil would work. You can also continue using bcrypt, by setting the password hash methods in the user schema module (per the Coherence migration guide):
defmodule MyApp.User do
use Ecto.Schema
use Pow.Ecto.Schema,
password_hash_methods: {&Comeonin.Bcrypt.hashpwsalt/1,
&Comeonin.Bcrypt.checkpw/2}
# ...
end
The reason it doesn’t just deny access with an invalid password hash is that there is no reset password functionality in core Pow (it’s an extension to Pow), and you probably do want to get an error to bubble up if there is inconsistency.