Guardian.Plug.sign_in is not injecting permissions

[Pjino]

I'm using and updated version of the Guardian example it seems that whatever combination of permissions I try to inject (for instance, "Guardian.Plug.sign_in(user, :token, perms: %{ default: :write_profile })" it won work.
When inspecting claims I always see: ..."pem" => %{"default" => -1},

[hassox]

Hi @Pjino. What version are you currently using? Can I see your config for guardian?

[Pjino]

Hi @hassox. I'm using the latest version of everything (Guardian, Phoenix,...) and I (think) I made all the necessary changes.
My config.exs looks like this:

and my controller is:

[hassox]

Thanks. Just an FYI you have two hooks declared.

The reason you're seeing the -1 is because you're setting the default permissions to Guardian.Permissions.max in sign in. If you had this instead do you still see -1?

Guardian.Plug.sign_in(user, :token, perms: %{ default: [:write_profile] })

[Pjino]

I changed it to:
Guardian.Plug.sign_in(user, :token, perms: %{ default: [:write_profile] })

and:
Guardian.Plug.sign_in(user, :token, perms: %{ default: [:read_profile, :write_profile] })

And it still's the same. I even created new users for each case but nothing changed.


My hooks are:

[yuyabee]

I think I'm seeing the same issue.
In IEx, Guardian.Permissions.to_value [:read_profile, :write_profile], :default returns 0, and Guardian.Permissions.availble returns [] where it's supposed to return list of permissions.
I have exact the same configuration as the permission example in the document.
@Pjino please try these functions and see if we are talking about the same problem.

[Pjino]

@yuyabee Yes, Guardian.Permissions.to_value [:read_profile, :write_profile], :default returns 0 and Guardian.Permissions.availble returns an error: UndefinedFunctionError

[yuyabee]

@Pjino Sorry, that was a typo, it's Guardian.Permissions.available

[Pjino]

@yuyabee Yes, it returns []. Sorry for testing it in such a rush that I didn't even try to see why it returned undefined...It was obvious:)

[hassox]

I haven't been able to repeat this locally :( I'm guessing that you're running Guardian 0.6.1 which was a bit buggy. GuardianDb was requiring this version. I've updated GuardianDb to rely on 0.6.2 in v 0.1.2. Can you please update guardian db and guardian and see if you still have the same issue?

[yuyabee]

@hassox Yes that was it. Upgrading to 0.6.2 solved it. Thank you so much.

[hassox]

Phew! Thanks so much for looking into it :)