Receiving a `secret_not_found` message on login action

mc962 commented 5 years ago

I've been trying guardian on an app together with absinthe to make a GraphQL API Phoenix application.

I got most of it working, and even the sign_up action works as expected. However, for the login action I am receiving a secret_not_found message in the response (no errors in the console).

From what I can tell, I am probably having an issue with guardian, as the message seems to be from either: jwt.ex and/or token.ex

but I'm not really sure what issue I'm having, as from what I can tell, it's all set up more or less correctly. I did see this git issue with a similar error message, but I think I'm not having the same problems, as my Guardian module looks set up correctly from what I can see.

Here is the app: https://github.com/mc962/guack

yordis commented 5 years ago

@mc962 your config looks fine except that I don't know if this is happening on production. This definitely seems to be something on your side.

mc962 commented 5 years ago

It's on a dev environment.

Do you know what theoretically could be causing it to happen? Unfortunately I don't have as much experience with this package's codebase/elixir in general, so I'm not positive where to look aside from what I've already mentioned. My understanding is that it's not picking up some secret somewhere, such as my secret_key in dev.exs, but I'm not quite sure where it's getting lost/why.

yordis commented 5 years ago

Check the name of your OTP, the name of your module and so on

mc962 commented 5 years ago

🤦‍♂️ 🤦‍♂️ 🤦‍♂️ Found it, it was the name of the module after all.

I had been using a context called Authentication, where the Guardian module was namespaced behind that module.

But my dev.exs config was asking for MyAppName.Guardian, instead of what I had, which was MyAppName.Authentication.Guardian. That's what I get for trying to be organized 😆

Thanks for the advice.

ueberauth / guardian

Receiving a `secret_not_found` message on login action #559