api_guard VS JWT

I built a Rails authenticated API for my react native app using api_guard (https://github.com/Gokul595/api_guard) and it works great. I evaluated a lot of different solutions (knock, devise, jwt_sessions, etc.) and api_guard has the best features out of the box for JWT and easy to set up. If you are thinking about option 2, look into api_guard.

https://github.com/Gokul595/api_guard is a nice little gem for API auth using JWTs. Most of it is honestly not that hard to implement yourself though

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.