Ruby Quickstart

This guide will help you integrate Descope's Ruby SDK into your backend application. Follow the steps below to get started.

Install Backend SDK

Install the SDK with the following command:

Terminal

gem install descope

Import and Setup Backend SDK

You'll need import and setup all of the packages from the SDK.

If you're using a CNAME with your Descope project, make sure to export the Base URL (e.g. export DESCOPE_BASE_URI="https://api.descope.com") when initializing descope_client.

app.rb

require 'descope'
 
descope_client = Descope::Client.new(
  {
    project_id: '__ProjectID__'
  }
)

Implement Session Validation

You will need to then fetch the session token from the Authorization header of each request, and use the SDK to validate the token.

The frontend SDK will store the session token in either a cookie or your browser's local storage. If using a cookie, the token will be sent to your app server automatically with every request.

app/controllers/application_controller.rb

class ApplicationController < ActionController::Base
  before_action :validate_session
 
  private
 
  def validate_session
    session_token = request.headers['Authorization']
    return head :unauthorized unless session_token
 
    begin
      jwt_response = $descope_client.validate_session(session_token: session_token)
      @current_user = jwt_response
    rescue Descope::AuthException
      head :unauthorized
    end
  end
end

It's important to validate the aud claim in your session token to ensure the token was issued for your specific application. This prevents token reuse across different applications. You can use JWT Templates to customize the aud claim.

Here's how to validate the session token with an aud claim:

app/controllers/application_controller.rb

class ApplicationController < ActionController::Base
  before_action :validate_session
 
  private
 
  def validate_session
    session_token = request.headers['Authorization']
    return head :unauthorized unless session_token
 
    begin
      jwt_response = $descope_client.validate_session(
        session_token: session_token,
        audience: '__ProjectID__'
      )
      @current_user = jwt_response
    rescue Descope::AuthException
      head :unauthorized
    end
  end
end

If you're interested in offline JWT validation, check out our offline JWT validation guide.

Once you've implemented the basic session validation, you can enhance your application with these additional features:

User Management

Learn how to create, update, and manage users in your application.

Role-Based Access Control

Implement fine-grained access control using roles and permissions.

API Gateway Session Validation

Secure your API endpoints with session validation middleware.

Set up M2M Authentication

Implement M2M authentication with Descope.

Additional Resources

Have You Implemented the Frontend Yet?

When integrating Descope into your application, you have three options depending on how much control you want over your frontend authentication experience and session management:

Option	Description	Best For
Use Descope Flows	Design your authentication screens and flows visually in the Descope Console with little or no frontend code. We handle all session management for you.	Fastest setup with minimal custom frontend work.
Use Descope Client SDKs	Build your own login screens and authentication experiences in your frontend using code, while relying on Descope's SDKs to manage sessions (login, logout, refresh).	Customizable UX with simplified session handling.
Use Descope Backend SDKs	Build your own frontend and your own backend APIs for authentication. You fully manage sessions, tokens, and authentication logic yourself.	Maximum flexibility and control, at the cost of more engineering effort.

Descope Flows

Design login screens and authentication flows visually without writing code, and embed them into your app.

Descope Client SDKs

Build custom login screens in your frontend using code, while we manage session tokens and refreshing for you.

Was this helpful?