JWT VS devise-jwt

To authenticate our users, we need to add jwt gem to our Gemfile

jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard. bcrypt is a Ruby binding for the OpenBSD bcrypt() password hashing algorithm.

ruby-jwt is fairly easy to use on it's own without Devise. You might try that first and only add Devise if needed.

Generally speaking, the larger the application, the more internal and external services it has to talk to. External services usually have their own way of authenticating and authorizing third party API calls. With internal systems however, organisations prefer to use JWT tokens because of their inherent flexibility and versatility. A sample JWT based handshake between 2 rails applications using ruby-jwt would look like this -

Interesting. What's the difference between this and the standard ruby-jwt? https://github.com/jwt/ruby-jwt

jwt - encoding and decoding jwt oauth

Decoding JWTs is simple whit the help of an already implemented solution. In this section, I'll be using the ruby-jwt.

The devise-jwt gem is an extension of Devise that will allow us to work with JWT tokens. Add the gems to Gemfile, then run bundle install:

En config/application.rb tenía la línea config.middleware.use ActionDispatch::Cookies para solucionar me funcionó esta respuesta de este hilo

There is a known issue, at least I had issues with it: https://github.com/waiting-for-dev/devise-jwt/issues/235. This issue seems to be rails relevant, not devise-jwt

I am currently working on developing and api using grape and devise jwt for user user authentication.

have you looked at https://github.com/waiting-for-dev/devise-jwt or https://github.com/lynndylanhurley/devise_token_auth

I think I saw a discussion on this here.

Something like https://github.com/waiting-for-dev/devise-jwt makes it fairly straight forward to implement auth with jwt through devise. Read the docs for the gem and you're 80% there.

I use this devise-jwt here: https://github.com/waiting-for-dev/devise-jwt