Two factor authentication extension for Devise

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tree: 4d0acf1ddd

for_activeadmin

get_specs_running

master

list

v1.1

v1.1.1

v1.1.2

v1.1.3

v1.1.4

v1.1.5

v2.0

v2.0.1

v2.1.0

v2.1.1

v2.2.0

version

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '4d0acf1ddd'

${ noResults }

two_factor_authentication/spec

History

Moncef Belyamani 4d0acf1ddd Allow executing code after sign in and before sign out ... **Why** In some cases, it might be necessary to run some code right after the user signs in, but before the OTP is sent, and also right before a user signs out. For example, consider this scenario: - The app requires the user to confirm their phone number before it gets saved. This confirmation is done by sending an OTP to the phone and asking the user to enter it. - User mistypes the number, then closes the anonymous browser window, or signs out before confirming - User signs back in, and OTP is sent to the mistyped number. User is now unable to fully sign in since the OTP is being sent to the wrong number In order to prevent this scenario, we need to be able to reset the `unconfirmed_mobile` to nil before the OTP is sent, and before they sign out so that they can type it in again. **How** Allow the gem user to define an OtpSender class with a `reset_otp_state` method		9 years ago
..
controllers	update rspec to version 3	11 years ago
features	Allow executing code after sign in and before sign out	9 years ago
lib/two_factor_authentication/models	Test against Ruby 2.2 and Rails 4.2	10 years ago
rails_app	Allow executing code after sign in and before sign out	9 years ago
support	Sign in or Log in button indifferent	10 years ago
spec_helper.rb	Add support for remembering a user's 2FA session in a cookie	10 years ago