BigW Consortium Gitlab

  1. 06 Jun, 2016 2 commits
    • Implement U2F registration. · 128549f1
      Timothy Andrew authored
      - Move the `TwoFactorAuthsController`'s `new` action to `show`, since
        the page is not used to create a single "two factor auth" anymore. We
        can have a single 2FA authenticator app, along with any number of U2F
        devices, in any combination, so the page will be accessed after the
        first "two factor auth" is created.
      - Add the `u2f` javascript library, which provides an API to the
        browser's U2F implementation.
      - Add tests for the JS components
    • Add a `U2fRegistrations` table/model. · 791cc913
      Timothy Andrew authored
      - To hold registrations from U2F devices, and to authenticate them.
      - Previously, `User#two_factor_enabled` was aliased to the
        `otp_required_for_login` column on `users`.
      - This commit changes things a bit:
          - `User#two_factor_enabled` is not a method anymore
          - `User#two_factor_enabled?` checks both the
            `otp_required_for_login` column, as well as `U2fRegistration`s
          - Change all instances of `User#two_factor_enabled` to
            `User#two_factor_enabled?`
      - Add the `u2f` gem, and implement registration/authentication at the
        model level.
  2. 31 May, 2016 1 commit
  3. 30 May, 2016 1 commit
  4. 13 May, 2016 1 commit
  5. 03 May, 2016 1 commit
  6. 14 Apr, 2016 3 commits
  7. 09 Apr, 2016 1 commit
  8. 20 Mar, 2016 1 commit
  9. 19 Mar, 2016 1 commit
  10. 11 Mar, 2016 2 commits
  11. 10 Mar, 2016 2 commits
  12. 09 Mar, 2016 1 commit
  13. 19 Feb, 2016 1 commit
  14. 15 Feb, 2016 2 commits
  15. 04 Feb, 2016 2 commits
  16. 03 Feb, 2016 1 commit
  17. 22 Jan, 2016 2 commits
  18. 21 Jan, 2016 2 commits
  19. 20 Jan, 2016 2 commits
  20. 13 Jan, 2016 1 commit
  21. 08 Jan, 2016 1 commit
  22. 07 Jan, 2016 1 commit
    • Sort by ID when sorting using "Recently created" · 9dacc3bc
      Yorick Peterse authored
      Sorting by "id" has the same effect as sorting by created_at while
      performing far better and without the need of an extra index (in case
      one wanted to speed up sorting by "created_at").
      
      Sorting by "Recently updated" still uses the physical "updated_at"
      column as there's no way to use the "id" column for this instead.
  23. 24 Dec, 2015 4 commits
  24. 15 Dec, 2015 1 commit
  25. 17 Nov, 2015 1 commit
  26. 02 Nov, 2015 1 commit
  27. 21 Oct, 2015 1 commit