Commit graph

5 commits

Author SHA1 Message Date
Timothy Andrew
dbedf3a61b Address review comments from @smcgivern.
1. Remove an unnecessary (since we're fetching all the records anyway)
   `pluck` while fetching U2F registration records.

2. Align "Your device was successfully set up!" section with the "U2F
   Devices" table below.
2016-08-18 22:12:02 +05:30
Timothy Andrew
16c44a5ddd Allow naming U2F devices.
1. Display a list of U2F devices on the `two_factor_auth` page.

2. Allow deleting individual U2F devices.

3. Allow setting a (optional) name for a device (during registration).
2016-08-18 22:12:02 +05:30
Timothy Andrew
fbb0612593 Don't allow clicking on "Setup New U2F Device" unless an authenticator app has been set up.
- Also change the help message to indicate that an authenticator app is
  now a prerequisite for U2F.
2016-06-15 08:16:11 +05:30
Timothy Andrew
86b07caa59 Implement authentication (login) using a U2F device.
- Move the `authenticate_with_two_factor` method from
  `ApplicationController` to the `AuthenticatesWithTwoFactor` module,
  where it should be.
2016-06-06 12:50:31 +05:30
Timothy Andrew
128549f10b Implement U2F registration.
- 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
2016-06-06 12:50:31 +05:30