Devise MailChimp adds a MailChimp option to devise that easily enables users to join your mailing list when they create an account.

Devise MailJet adds a MailJet option to devise that easily enables users to join your mailing list when they create an account.

A simple way to have Devise capture important marketing data.

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.

ORM file for using Devise with MongoMapper

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.

Devise OAuth2 Facebook extension

Devise OAuth2 Facebook extension for rails 3 and mongoid

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

add OAuth2 authentication to rails3 application

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.

Reusable Omniauth integration for Devise supporting multiple providers. Essentially takes the how-to setup in the devise wiki for facebook and other providers and gives you code in your application to get started with.

Reusable Omniauth integration for Devise supporting multiple providers. Essentially takes the how-to setup in the devise wiki for facebook and other providers and gives you code in your application to get started with.

This Devise extension adds the ability for users to authenticate with one-time passwords, enabling a more secure session mechanism. When logging in, users will receive a unique one-time password that they can use to access the system. This password is valid for only one use, ensuring that each login is secure and that users cannot reuse an old password to access their account. This extension provides a simple and effective way to improve the security of your application and protect against password attacks.

OTP authentication for Devise

Time Based OTP/rfc6238 compatible authentication for Devise