Rollouts (feature flags) for Rails.

Enables sending simple emails to app owners. Wraps [Leadersend](http://www.leadersend.com) mail delivery service and defines a DevelopmentNotification::Email model for logging.

Auth0 authentication for devise

Authenticate requests using an Auth0 JWT passed by HTTP header

Customize basic auth header when using token_authenticatable with devise.

I18n support for devise views based on Twitter Bootstrap 3

Authenticate users against an IMAP server

Instant 2FA plugin for devise

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

Cookie-based JWT authentication for devise with configurable token revocation strategies, forked from devise-jwt-cookie

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.

Devise extension to allow authentication via LDAP, No ORM

This app closes the gap between the huge world of ruby and meteor through devise. Simply install, configure and use it to connect to your desired meteor server.

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.

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.

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