JWT not returning on sign up or sign in about devise-jwt

[waiting-for-dev]

Hi @bin4ryio .

Usually, if you just want the jwt token to be dispatched in a regular sign_in and to be revoked in a regular sign_out, there is no need to manually configure jwt.dispatch_requests neither jwt.revocation_requests, as they are detected automatically.

Also, note that you have a typo. It is request_formats and not requests_formats (the extra s).

So, I think that with following configuration it should work:

config.jwt do |jwt|
    # jwt.secret = ENV['DEVISE_JWT_SECRET_KEY']
    jwt.secret = "d8f531be58ad478cc79d072d6c4ea777a0c6ca5fbd9a2194b6fbfcea5f4f122017092a593f31576a0c27d9478f1bd74d336945481d22c7f9af36fd2fa6061c3d"
    jwt.request_formats = { user: [:json] }
  end

[waiting-for-dev]

Going to close it now. Feel free to come back with more questions.

[darr1s]

Hello, thanks the the prompt reply @waiting-for-dev. However, I have checked my devise.rb and the typo was not there. It was written jwt.request_formats = { user: [:json] } and the problem continue to persist.

[waiting-for-dev]

Can you copy/paste here which configuration do you have now?

[darr1s]

I still could not understand why it return unexpected ''. May I ask if your environment is Rails API or Rails default?

Here's the gist:
https://gist.github.com/bin4ryio/7a4c9bf1b8d5ec1dbbd195dd06ad26e1

Thanks.

[darr1s]

No clear advice given. But I'm able to get Bearer by adding :head on CORS config and it will not work if devise_for has a :path api/v1/users option. Thank you anyways.

[mits87]

Someone has full example of use this gem?

[waiting-for-dev]

Hey @bin4ryio . Sorry, I missed your last message. This gem should work with both Rails API or default.

Happy to see now it works for you. About the path option, it should also work with it. It would be useful if you could prepare an example application that reproduces the bug.

Cheers

[waiting-for-dev]

@mits87 , in spec/fixtures/rails_app/ you have an example application used for testing purposes. You only need to configure CORS on top of that if you are using cross domain requests. See rack-cors for that.

[darr1s]

Realize its my mistake for not reading correctly. Everything is working for intended now. Thanks for the great gem and prompt support @waiting-for-dev

I also use this to encode user's email into payload, maybe adding it to front-page to help beginner out.

   def jwt_payload
     { 'email' => email }
   end```

[waiting-for-dev]

Happy to hear that @bin4ryio :)

The information about the way to add custom claims to the payload is already in the README. Don't forget to call super if you are using JTIMatcher revocation strategy, though.

@bin4ryio could u please clarify how did u return authorization header