OAuth2 VS JWT

📝 Added OIDC documentation, example, and spec references in OIDC.md in PR #663

🔨 https://github.com/ruby-oauth/oauth2

See response_spec.rb, or the oauth-xx/snaky_hash gem for more ideas.

This project sits underneath a large portion of the authorization systems on the internet. According to GitHub's project tracking, which I believe only reports on public projects, 100,000+ projects, and 500+ packages depend on this project. That is a lot of things to upgrade.

Here's the gem I used. gem 'oauth2'

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.