[info] POST /api/sessions [debug] Processing with Chatty.SessionController.create/2 Parameters: %{"email" => "email@gmail.com", "password" => "[FILTERED]"} Pipelines: [:api] [debug] QUERY OK source="users" db=2.1ms SELECT u0."id", u0."email", u0."first_name", u0."last_name", u0."username", u0."p…

[image] rickmutua: What could be the issue? :erlang.apply/3 is called with wrong kind of arguments. Usually the first argument should be a module name. But how this actually happened remains to be unknown until you show us some more code, especially the Chatty.SessionController.create/2 mig…

sorry, added the Session and User Controller file

As I recall you have to define some kind of conversion file to convert a custom type like that user record into a JWT string and back again, can you show that module? (I might be mistaken on that but I thought it needed such a module?)

[image] rickmutua: new_conn = Guardian.Plug.sign_in(conn, user, :access) According to the (sparse) documentation, the second parameter to Guardian.Plug.sign_in/5 has to be an atom, but user (which is the result of Repo.insert/1) is a struct, not an atom. But as I said, documentation is very …

I don’t have a conversion module. didn’t see anywhere on the guardian documentation about converting but I will have a look around

Just a question I always ask when I see someone using Guardian: What functionality are you needing of JWT that a normal Phoenix Token doesn’t give you? If none then you really really should not be using Guardian as it is quite a bit more heavy-weight and geared toward specific purposes.

am fairly new to elixir and there is an app am trying to build and the closest tutorial I could get to what am trying to create uses Guardian so I decided to try it out. :man_shrugging:t5: looks like it wasn’t the smartest idea

[image] rickmutua: am fairly new to elixir and there is an app am trying to build and the closest tutorial I could get to what am trying to create uses Guardian so I decided to try it out. :man_shrugging:t5: looks like it wasn’t the smartest idea Guardian is fantastic for JWT uses, but for an…

the front-end is in react, instead of creating a new connection and signing in a user, am using Guardian’s refresh function, passing in the current jwt and claims, and receive a new jwt that is good for another 30 days. registration works but login fails after the user is created

Hmm, 30 days implies some kind of client-side storage for the token, are you using local storage? If you are using local storage how are you handling the security issues around storing secure data in it? If you are using cookies then why not just use Phoenix’s standard session handling (which is a…

Elixir Programming Language Forum

Argument error whenever I try to login

Questions & Help Questions

rickmutua July 4, 2018, 7:36am 13

Fixed it