Backend

JWT Authentication in Ruby on Rails: Complete Guide

Ruby on Rails is a full-stack web framework. JWT authentication in Rails API mode is commonly implemented with the jwt gem for stateless token-based auth. This guide walks you through everything you need to implement robust JWT authentication in Ruby on Rails, from choosing the right library to writing production-ready code.

Recommended JWT Library for Ruby on Rails

jwt (ruby gem)

The recommended library for handling JWT authentication in Ruby on Rails. It provides a mature API, active maintenance, and wide community adoption — making it the go-to choice for production applications built with Ruby on Rails.

Whether you are building a small prototype or a large-scale enterprise application, jwt (ruby gem) gives you the tools to generate, sign, verify, and decode JWT tokens with confidence. It supports all major signing algorithms including HS256, RS256, and ES256, and integrates naturally with the Ruby on Rails ecosystem.

JWT Authentication Code Example

Below is a practical code example showing how to implement JWT authentication in Ruby on Rails using jwt (ruby gem). This snippet demonstrates the core pattern you will use in most applications:

Ruby on Rails — JWT Examplejwt (ruby gem)

class AuthToken
  SECRET = Rails.application.credentials.secret_key_base

  def self.encode(payload, exp = 24.hours.from_now)
    payload[:exp] = exp.to_i
    JWT.encode(payload, SECRET, 'HS256')
  end

  def self.decode(token)
    decoded = JWT.decode(token, SECRET, true, algorithm: 'HS256')
    HashWithIndifferentAccess.new(decoded.first)
  rescue JWT::ExpiredSignature
    nil
  rescue JWT::DecodeError
    nil
  end
end

This example shows the essential JWT workflow in Ruby on Rails. In production, make sure to store secrets in environment variables, use HTTPS, and implement proper error handling for token expiration and revocation.

How to Set Up JWT in Ruby on Rails

Follow these steps to get JWT authentication working in your Ruby on Rails project. Each step builds on the previous one, so we recommend following them in order:

1
Add jwt gem to Gemfile: gem 'jwt'
2
Create AuthToken service class for encode/decode
3
Add before_action :authenticate_user! in controllers
4
Implement login action returning token JSON
5
Set up token refresh endpoint

Key Features of JWT Auth in Ruby on Rails

When you implement JWT authentication in Ruby on Rails, you gain access to several powerful capabilities that make your application more secure and scalable:

API-only mode support

Token encode/decode service

Before_action auth filter

Token expiration handling

Why Use JWT Authentication in Ruby on Rails?

Ruby on Rails is widely used for building modern web applications and APIs, and JWT has become the de facto standard for stateless authentication. By combining Ruby on Rails with JWT, you get a scalable authentication system that does not require server-side session storage.

JWT tokens are self-contained, meaning they carry all the information needed to identify a user and their permissions. This makes them ideal for microservice architectures, mobile backends, and single-page applications built with Ruby on Rails. Each request includes the token, so your server can verify identity without a database lookup.

The jwt (ruby gem) library makes it straightforward to implement JWT in Ruby on Rails. You can generate tokens on login, verify them on each request, and handle token refresh to keep users authenticated without interruption. Combined with proper security practices — such as short expiration times, refresh token rotation, and secure storage — JWT provides a robust foundation for any authentication system.

Best Practices for JWT in Ruby on Rails

When implementing JWT authentication in Ruby on Rails, follow these best practices to keep your application secure:

Use strong secrets: Always use a long, random secret key for signing tokens. Store it in environment variables, never in source code.
Set short expiration times: Access tokens should expire quickly (15–30 minutes). Use refresh tokens for longer sessions.
Validate on every request: Always verify the token signature and check expiration before granting access to protected resources.
Use HTTPS: JWT tokens sent over plain HTTP can be intercepted. Always use HTTPS in production to protect tokens in transit.
Handle token refresh: Implement a refresh token flow so users are not logged out when their access token expires. Rotate refresh tokens to prevent replay attacks.
Do not store sensitive data in tokens: JWT payloads are Base64-encoded, not encrypted. Avoid putting passwords or other sensitive information in claims.

Decode & Inspect JWT Tokens Instantly

Use our free online JWT Decoder to inspect any token — view the header, payload, claims, and expiration status right in your browser. No sign-up required.

Try JWT Decoder Pro →