If you like to use Devise, but wish it had an easy token authentication system that handles a user logging in from multiple devices, DeviseMultipleTokenAuth is for you.

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

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.

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.

Adds one time token authentication to devise

Extension for devise to provide password change without using registerable.

A plugin to devise that will expire user passwords after a set amount of time and prompt them to update their password.

A devise extension to curb password sharing.

It sends verification code via SMS (using Twilio). User enters the code to confirm the phone number.

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

== Devise::Revokable A module for Devise[http://github.com/plataformatec/devise] This gem was created by "borrowing" heavily from Devise::Invitable[http://github.com/scambra/devise_invitable] It exists to extend Devise to provide the basis for what is essentially the reverse of the standard <tt>confirmable</tt> module. Where <tt>confirmable</tt> sends an email and awaits a response, before confirming a new registration, <tt>revokable</tt> allows immediate access and sends an email which provides a link to "revoke" the account if it was created fraudulently. This is useful if you want to lower the barrier to entry to creating accounts, and clearly, if account security isn't a concern. Note that tests are non-existent. Use freely but at your own risk. === Configuring It works like normal Devise modules. Add the <tt>:revokable</tt> module to the declaration. # in user.rb devise :revokable # plus other devise modules If the user who received the revocation email follows the provided link and confirms revocation, the account will effectively be "revoked" and inactive, unable to log in. Additionally, you may want to override <tt>#revoke!</tt> to perfom additional revocation on the account, e.g. deleting posts made, resetting personal information, etc. The super method yields to a block for this purpose. # in user.rb def revoke! super do self.some_method_that_resets_me! end end That's about the extent of it. As with typical devise modules you can override the mailers and views with your own. Additionally you can define the module accessor <tt>@@mailer</tt> on the module with a proc to handle your mail if you need to. This proc is yielded two arguments, the method name (e.g. :revocation_instructions), and the affected resource. # in config/initializers/devise_revokable.rb require 'devise_revokable' require 'my_mailer' DeviseRevokable.mailer = proc {|method_name, resource| MyMailer.send(:method_name, resource) }

Gem that helps you to organaize your users with roles and manipulate them. Visit HOMEPAGE for more information how to use this gem.