Question 1

How to add a username field to Devise sign up?

Accepted Answer

Override the default parameters in ApplicationController using devise_parameter_sanitizer.permit for :sign_up, as shown in the Strong Parameters section. You'll need to run a migration to add the field to your model and update views if using custom ones.

Question 2

Devise vs Sorcery for Rails authentication?

Accepted Answer

Devise is more comprehensive with built-in modules for features like email confirmation and OmniAuth, while Sorcery is lighter and focuses on core authentication. Choose Devise for full-featured, production-ready auth, or Sorcery if you need minimal overhead and prefer to build custom flows.

Question 3

How to set up OmniAuth with Devise for GitHub login?

Accepted Answer

Add the Omniauthable module to your model and configure it in devise.rb with your app credentials, as detailed in the OmniAuth section. You'll also need to handle callbacks in a custom controller if beyond basic setup.

Question 4

How to test user login in Rails with Devise?

Accepted Answer

Use the included test helpers like sign_in and sign_out from Devise::Test::IntegrationHelpers for integration tests, and include them in your test configuration as described in the 'Test helpers' part of the README.

Question 5

Can Devise handle multiple user roles like admin and user?

Accepted Answer

Yes, Devise supports multiple models with separate authentication logic, as shown in 'Configuring multiple models'. You can generate different models (e.g., User and Admin) and use scoped helpers like current_admin and before_action :authenticate_admin!.

Question 6

Why is my Devise password reset email not sending?

Accepted Answer

Check your mailer configuration in environments files for default_url_options, ensure Active Job is set up if using deliver_later, and verify that the Recoverable module is enabled in your model. Also, inspect logs for errors as tokens might be exposed if log level is too low.

Question 7

How to use Devise with Rails API only mode?

Accepted Answer

Enable HTTP Basic Authentication in the initializer with config.http_authenticatable = [:database], but note that email-based flows aren't fully supported. You may need custom Warden strategies for token auth, and adjust middleware for testing as per the API mode section.

Devise

What is Devise?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions