devise-otp 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 68e7b6bff6340dae80c51a03b25daa473524eee4
-  data.tar.gz: 1407a2855ebf8bd2df27e678bf1b360922e894eb
+SHA256:
+  metadata.gz: 6b5132454cb31efb85ab78d8a0866c6e98e3e3fc8f9c51fa770b735e59a0d976
+  data.tar.gz: ef69e79487527616462f0c3c918094a9338ede9b59a8aef005b34549ae231166
 SHA512:
-  metadata.gz: 4f233eb0d98a0ec858a27711f355d7ab6306d358b0f0ea80008616c06904ad917b7becfe6f988f51b930627bb6126fa8cc3d23e73b2deb8588fe10d2e963a454
-  data.tar.gz: fab7310046129c7f095493f0505a3b1b16906608165f0ee446c6afc3980b34e9a0683da2553ac9cec7c80baa409a09305b7abd68c985e4d397384a9d57471a38
+  metadata.gz: 7312e301fb3a313056878b4e7d067ed78ad37717fbb632b27e9dce05d7bd77e8b972bdbcb8ff189800509ef65d74c99773c650cebc881756d5c9a5456b0c2578
+  data.tar.gz: 7e1f0bb51e8c805f6e95eb4cc61231e3bcfd9562ac0c523ee3f60221cea9b56891f42badb66ed7b3bc986fec63cd9164100b72822d26ede99fda7a7029f29f38

data/.github/workflows/ci.yml

@@ -0,0 +1,36 @@
+---
+name: CI
+
+on:
+  - push
+  - pull_request
+
+jobs:
+  rspec:
+    runs-on: ubuntu-20.04
+    strategy:
+      fail-fast: false
+      matrix:
+        ruby:
+          - '3.1'
+          - '3.0'
+          - '2.7'
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+
+      - name: Setup Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+
+      - name: Bundle
+        run: |
+          gem install bundler
+          bundle install --jobs 4 --retry 3
+
+      - name: Run tests
+        env:
+          DEVISE_ORM: active_record
+        run: rake test

data/Gemfile

@@ -1,25 +1,4 @@
-source 'https://rubygems.org'
+source "https://rubygems.org"
 
 # Specify your gem's dependencies in devise-otp.gemspec
 gemspec
-
-gem "rdoc"
-
-group :test do
-  platforms :jruby do
-    gem 'activerecord-jdbcsqlite3-adapter'
-  end
-
-  platforms :ruby do
-    gem "sqlite3"
-  end
-
-  gem "rails", "~> 4.0.0"
-
-  gem "capybara"
-  gem 'shoulda'
-  gem 'selenium-webdriver'
-
-  gem 'minitest-reporters', '>= 0.5.0'
-
-end

data/README.md

@@ -1,38 +1,38 @@
 # Devise::Otp
-[![Build Status](https://travis-ci.org/wmlele/devise-otp.png?branch=master)](https://travis-ci.org/wmlele/devise-otp)
 
-Devise OTP implements two-factors authentication for Devise, using an rfc6238 compatible Time-Based One-Time Password Algorithm.
-It uses the [rotp library](https://github.com/mdp/rotp) for generation and verification of codes.
+Devise OTP is a two-factors authentication extension for Devise. The second factor is done using an [RFC 6238](https://datatracker.ietf.org/doc/html/rfc6238) Time-Based One-Time Password (TOTP) implemented by the [rotp library](https://github.com/mdp/rotp).
 
-It currently has the following features:
+It has the following features:
 
-* Url based provisioning of token devices, compatible with **Google Authenticator**.
-* Two factors authentication can be **optional** at user discretion, **recommended** (it nags the user on every sign-in) or **mandatory** (users must enroll OTP after signing-in next time, before they can navigate the site). The settings is global, or per-user.
-* Optionally, users can obtain a list of HOTP recovery tokens to be used for emergency log-in in case the token device is lost or unavailable.
+- Optional and mandatory OTP enforcement
+- Setting up trusted browsers for limited access
+- Generating QR codes
 
-Compatible token devices are:
+Some of the compatible token devices are:
 
 * [Google Authenticator](https://code.google.com/p/google-authenticator/)
-* ...
+* [FreeOTP](https://fedorahosted.org/freeotp/)
 
-## Quick overview of Two Factors Authentication, using OTPs.
+Device OTP was recently updated to work with Rails 7 and Turbo.
 
-* A shared secret is generated on the server, and stored both on the token device (ie: the phone) and the server itself.
+## Two-factors authentication using OTP
+
+* A shared secret is generated on the server, and stored both on the token device (e.g. the phone) and the server itself.
 * The secret is used to generate short numerical tokens that are either time or sequence based.
 * Tokens can be generated on a phone without internet connectivity.
 * The token provides an additional layer of security against password theft.
 * OTP's should always be used as a second factor of authentication(if your phone is lost, you account is still secured with a password)
 * Google Authenticator allows you to store multiple OTP secrets and provision those using a QR Code
 
-Although there's an adjustable drift window, it is important that both the server and the token device (phone) have their clocks set (eg: using NTP).
-
+*Although there's an adjustable drift window, it is important that both the server and the token device (phone) have their clocks set (eg: using NTP).*
 
 ## Installation
 
-Add this line to your application's Gemfile:
+If you haven't, set up [Devise](https://github.com/heartcombo/devise) first.
+
+To add Devise OTP, add this line to your application's Gemfile:
 
-    gem 'devise'
-    gem 'devise-otp'
+    gem "devise-otp"
 
 And then execute:
 
@@ -42,32 +42,11 @@ Or install it yourself as:
 
     $ gem install devise-otp
 
-
-### Devise Installation
-
-To setup Devise, you need to do the following (but refer to https://github.com/plataformatec/devise for more information)
-
-Install Devise:
-
-    rails g devise:install
-
-Setup the User or Admin model
-
-    rails g devise MODEL
-
-Configure your app for authorisation, edit your Controller and add this before_filter:
-
-    before_filter :authenticate_user!
-
-Make sure your "root" route is configured in config/routes.rb
-
-### Automatic Installation
-
 Run the following generator to add the necessary configuration options to Devise's config file:
 
     rails g devise_otp:install
 
-After you've created your Devise user models (which is usually done with a "rails g devise MODEL"), set up your Devise OTP additions:
+After you've created your Devise user models (which is usually done with a `rails g devise MODEL`), set up your Devise OTP additions:
 
     rails g devise_otp MODEL
 
@@ -75,50 +54,48 @@ Don't forget to migrate:
 
     rake db:migrate
 
-### Custom Views
+Add the gem's JavaScript to you `application.js`:
 
-If you want to customise your views (which you likely will want to), you can use the generator:
+    //= require devise-otp
 
-    rails g devise_otp:views
 
-### I18n
+### Custom views
 
-The install generator also installs an english copy of a Devise OTP i18n file. This can be modified (or used to create other language versions) and is located at: _config/locales/devise.otp.en.yml_
+If you want to customise your views, you can use the following generator to eject the default view files:
 
+    rails g devise_otp:views
 
-## Usage
+By default, the files live within the Devise namespace (`app/views/devise`, but if you want to move them or want to match the Devise configuration, set `config.otp_controller_path` in your initializers. 
 
-With this extension enabled, the following is expected behaviour:
+### I18n
+
+The install generator also installs an english copy of a Devise OTP i18n file. This can be modified (or used to create other language versions) and is located at: _config/locales/devise.otp.en.yml_
 
-* Users may go to _/MODEL/otp/token_ and enable their OTP state, they might be asked to provide their password again (and OTP token, if it's enabled)
-* Once enabled they're shown an alphanumeric code (for manual provisioning) and a QR code, for automatic provisioning of their authetication device (for instance, Google Authenticator)
-* If config.otp_mandatory or model_instance.otp_mandatory, users will be required to enable, and provision, next time they successfully sign-in.
+### QR codes
 
+By default, Devise OTP assumes that you use [Sprockets](https://github.com/rails/sprockets) to render assets and so will use the ([qrcode.js](/app/assets/javascripts/qrcode.js)) embeded library to render the QR code.
 
-### Configuration Options
+If you need something more, have a look at [QR codes](/docs/QR_CODES.md) documentation file.
 
-The install generator adds some options to the end of your Devise config file (config/initializers/devise.rb)
+## Configuration
 
-* config.otp_mandatory - OTP is mandatory, users are going to be asked to enroll the next time they sign in, before they can successfully complete the session establishment.
-* config.otp_authentication_timeout - how long the user has to authenticate with their token. (defaults to 3.minutes)s
-* config.otp_drift_window - a window which provides allowance for drift between a user's token device clock (and therefore their OTP tokens) and the authentication server's clock. (default: 3)
-* config.otp_credentials_refresh - Users that have logged in longer than this time ago, or haven't refreshed, are boing to be asked their password (and an OTP token, if enabled) before they can see or change their otp informations. (defaults to 15.minutes)
-* config.recovery_tokens - Whether the users are given a list of one-time recovery tokens, for emergency access (default: true)
-* config.otp_uri_application - The name of this application, to be added to the provisioning url as '<user_email>/application_name' (defaults to the Rails application class)
+The install generator adds some options to the end of your Devise config file (`config/initializers/devise.rb`):
 
-## Contributing
+* `config.otp_mandatory`: OTP is mandatory, users are going to be asked to enroll the next time they sign in, before they can successfully complete the session establishment.
+* `config.otp_authentication_timeout`: How long the user has to authenticate with their token. (defaults to `3.minutes`)
+* `config.otp_drift_window`: A window which provides allowance for drift between a user's token device clock (and therefore their OTP tokens) and the authentication server's clock. Expressed in minutes centered at the current time. (default: `3`)
+* `config.otp_credentials_refresh`: Users that have logged in longer than this time ago, are going to be asked their password (and an OTP challenge, if enabled) before they can see or change their otp informations. (defaults to `15.minutes`)
+* `config.otp_recovery_tokens`: Whether the users are given a list of one-time recovery tokens, for emergency access (default: `10`, set to `false` to disable)
+* `config.otp_trust_persistence`: The user is allowed to set his browser as "trusted", no more OTP challenges will be asked for that browser, for a limited time. (default: `1.month`, set to false to disable setting the browser as trusted)
+* `config.otp_issuer`: The name of the token issuer, to be added to the provisioning url. Display will vary based on token application. (defaults to the Rails application class)
+* `config.otp_controller_path`: The view path for Devise OTP controllers. The default being 'devise' to match Devise default installation.
 
-1. Fork it
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Create new Pull Request
+## Authors
 
-## Thanks
+The project was originally started by Lele Forzani by forking [devise_google_authenticator](https://github.com/AsteriskLabs/devise_google_authenticator) and still contains some devise_google_authenticator code. It's now maintained by [Josef Strzibny](https://github.com/strzibny/).
 
-I started this extension by forking [devise_google_authenticator](https://github.com/AsteriskLabs/devise_google_authenticator), and this project still contains some chunk of code from it, esp. in the tests and generators.
-At some point, my design goals were significantly diverging, so I refactored most of its code. Still, I want to thank the original author for his relevant contribution.
+Contributions are welcome!
 
 ## License
 
-MIT Licensed
+MIT Licensed

data/app/assets/javascripts/devise-otp.js

@@ -0,0 +1 @@
+//= require_tree .