benonymus
Protocol Enumerable not implemented for error with guardian login
Hey I a trying to make a login system for my phoenix app, but I am having an error on successful login attempt:
# protocol Enumerable not implemented for %Userteam1.Web.User{__meta__: #Ecto.Schema.Metadata<:loaded, "users">, id: 1, inserted_at: ~N[2018-08-19 09:10:38.661295], name: "bence", password: nil, password_hash: "$2b$12$EEH/mgGuM1GyKHkUSIJG..THKJ6W/0iN/tWH6FiikZ4dRjGqPwt3G", role: #Ecto.Association.NotLoaded<association :role is not loaded>, role_id: 1, team: #Ecto.Association.NotLoaded<association :team is not loaded>, team_id: nil, updated_at: ~N[2018-08-19 09:10:38.661303]}. This protocol is implemented for: DBConnection.PrepareStream, DBConnection.Stream, Date.Range, Ecto.Adapters.SQL.Stream, File.Stream, Function, GenEvent.Stream, HashDict, HashSet, IO.Stream, List, Map, MapSet, Postgrex.Stream, Range, Stream
my controller for login looks like this:
def create(conn, %{"session" => %{"name" => name, "password" => password}}) do
case Userteam1.Web.name_password_auth(name, password) do
{:ok, user} ->
IO.inspect(user)
conn
|> put_flash(:info, "Successfully signed in")
|> Guardian.encode_and_sign(user)
|> redirect(to: user_path(conn, :index))
{:error, _reason} ->
conn
|> put_flash(:error, "Invalid name or password")
|> render("new.html")
end
end
and my schema that it is trying to load looks like this:
schema "users" do
field(:name, :string)
field(:password_hash, :string)
field(:password, :string, virtual: true)
belongs_to(:role, Userteam1.Role)
belongs_to(:team, Userteam1.Team)
timestamps()
end
How can this be fixed?
Marked As Solved
stephane
Did you config guardian ? (config.exs)
config :my_app, MyApp.Guardian,
issuer: "my_app",
secret_key: "Secret key. You can use `mix guardian.gen.secret` to get one"
Also Liked
idi527
Dog.UserManager.Guardian.Plug != Guardian.Plug
Seems like you’ve confused one with the other because of
alias Dog.{UserManager, UserManager.User, UserManager.Guardian}
7stud
First time trying Guardian–I did not know that!
Seems like you’ve confused one with the other because of
alias Dog.{UserManager, UserManager.User, UserManager.Guardian}
And, I checked that line to make sure that Guardian.Plug was indeed equivalent to Dog.UserManager.Guardian.Plug! All that code is from the official Guardian “Getting Started Tutorial”.
And, the route problem I was having was due to the tutorial alternately using “/protected” and “/secret” to refer to the Guardian protected route.
By the way, things work when I do:
alias Dog.{UserManager, UserManager.User, UserManager.Guardian}
...
new_conn = Guardian.Plug.sign_in(conn, user)
So, I guess I was looking at the wrong docs??? This is what my lib/dog/user_manager/guardian.ex file looks like:
defmodule Dog.UserManager.Guardian do
use Guardian, otp_app: :dog
alias Dog.UserManager
def subject_for_token(user, _claims) do
# You can use any value for the subject of your token but
# it should be useful in retrieving the resource later, see
# how it being used on `resource_from_claims/1` function.
# A unique `id` is a good subject, a non-unique email address
# is a poor subject.
{:ok, to_string(user.id)}
end
def resource_from_claims(%{"sub" => id}) do
# Here we'll look up our resource from the claims, the subject can be
# found in the `"sub"` key. In `above subject_for_token/2` we returned
# the resource id so here we'll rely on that to look it up.
case UserManager.get_user(id) do
nil -> {:error, :user_not_found}
user -> {:ok, user}
end
end
end
I guess the line:
use Guardian, otp_app: :dog
injects a Plug module? I looked at the source code for the Guardian module:
defmacro __using__(opts \\ []) do
otp_app = Keyword.get(opts, :otp_app)
# credo:disable-for-next-line Credo.Check.Refactor.LongQuoteBlocks
quote do
@behaviour Guardian
if Code.ensure_loaded?(Plug) do
__MODULE__
|> Module.concat(:Plug)
|> Module.create( ## CREATES THE Dog.UserManager.Guardian.Plug MODULE
quote do
use Guardian.Plug, unquote(__MODULE__)
end,
Macro.Env.location(__ENV__)
)
end
And Guardian.Plug’s __using__() function looks like this:
defmacro __using__(impl) do
quote do
...
...
def sign_in(conn, resource, claims \\ %{}, opts \\ []),
do: Guardian.Plug.sign_in(conn, implementation(), resource, claims, opts)
And, there’s the two argument sign_in() function that I lucked into; and, like you said, the way I was calling it originally:
Guardian.Plug.sign_in(conn, Guaridan, user)
matched the parameter variable claims to user.
lol. And the original solution to this question was:
ok found something, I changed it into this:
|> Guardian.Plug.sign_in(user)
Thanks idiot!
NobbZ
Guardian.encode_and_sign/4 does not return a Plug.Conn.t, nor anything that would implement the Enumerable protocol.
Please give the Getting Started of guardian another read and try to incorporate the things you learned there into your application.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance








