This allows a Devise user’s validity to be restricted by a date range. This allows administrators to set up accounts that are valid to-, or from-, or between specific dates.

A gem to support duosecurity 2 factor auth.

Formtastic form builder for Devise with some extra features like full I18n support and dynamic page titles.

Track failed attempts to sign in through devise to allow for increased security measures, such as locking sign in after failed attempts on several accounts from a single IP address.

I18n support for devise views based on Twitter Bootstrap 3

Authenticate users against an IMAP server

Interacts with the ruby-jira gem to provide authentication of a login against a JIRA system.

Supports silent refresh with client side single page apps in mind.

A gem to generate documentation out of tests.

Devise extension to allow authentication to multiple LDAP servers, or with multiple configurations to the same LDAP server. Fork of the devise_ldap_authenticatable project.

It adds support to devise for confirming users' mobile by SMS.

A Devise plugin for exposing multiple authentication providers via omniauth.

A new authentication strategy named radius_authenticatable is added to the list of warden strategies when the model requests it. The radius server information is configured through the devise initializer. One or more servers may be configured. When a user attempts to authenticate via radius, the radiustar gem is used to perform the authentication with each server until a response is received. This authentication strategy can be used in place of the database_authenticatable or alongside it depending on the needs of the application.

Authentication strategy for devise based on headers, passed by Oracle Access Manager.

The OAuth 2.0 Authorization Framework draft-ietf-oauth-v2-28 implementation on top of devise.

Rails 4 engine that adds OAuth2 Provider support to any application built with Devise authentication

There are plenty of gems out there that deal with being an OAuth2 "consumer", where you redirect users to an OAuth2 "provider", allowing you to hand off authentication to a separate service. There are also plenty of gems that set you up as your own OAuth2 provider. ***BUT***, what happens when you want to separate your "authentication" server from your "resource" server? This gem is meant to be used on an API "resource" server, where you want to accept OAuth Access Tokens from a client, and validate them against a separate "authentication" server. This communication is outside the scope of the official OAuth 2 spec, but there is a need for it anyway.

Time Based OTP/rfc6238 compatible authentication for Devise

Time Based OTP/rfc6238 compatible authentication for Devise with Devise 4.2 and Rails 5 compatibility. Drop-in replacement for devise-otp.

Allows Devise to authenticate users from central-authentication services like LDAP and Shibboleth.