devise-two-factor
devise-two-factor copied to clipboard
tinfoil
Barebones two-factor authentication with Devise
I've setup this gem before and write some tests. Now, when I updated to Rails `6.1.3` tests have been failing. ### Expected behavior I expect the `otp_provisioning_uri` returns the correct...
This uses SecureRandom under the hood and provides more randomness per character.
I'm just following the readme to setup devise-two-factor. To setup encryption one should setup db encryption by issuing following command: ``` rails db:encryption:init ``` On Rails 6 this fails with:...
When using devise-two-factor with devise lockable, there are somehow two calls being made to validate/valid_for_authentication? - the latter of which is doing the failed_attempts increment. The first failed_attempts increment happens...
Hi, When I run the generator ``` ./bin/rails generate devise_two_factor user ``` It adds the following code to `config/initializers/devise.rb` file: ``` config.warden do |manager| manager.default_strategies(:scope => :user).unshift :two_factor_authenticatable end ```...
One of the more useful features of common sites that use 2FA is that they provide an option to remember the device as a trusted device. Users are still prompted...
After successful 2fa authentication, devise basically for some reason device grabs warning from locale path d**evise.failure.already_authenticated** instead notice from **devise.sessions.signed_in** Here's my controller concern: ```ruby module AuthenticateWithOtpTwoFactor extend ActiveSupport::Concern def...
I'm currently on Rails 6.1 and devise-two-factor 4.0.2 I see what looks like a bit of contradiction in your docs: https://github.com/tinfoil/devise-two-factor/blob/main/CHANGELOG.md#402 says that 4.0.2 "Adds Rails 7.0 support" But then...
Both the upcoming Rails 7 `ActiveRecord::Encryption` module and `attr_encrypted` use a class attribute named `encrypted_attributes` which leads to all sorts of issues when you use `attr_encrypted` on any Rails 7...
