- 17 Sep, 2018 1 commit
-
-
Marcel Amirault authored
-
- 28 Feb, 2018 1 commit
-
-
Connor Shea authored
-
- 08 Sep, 2017 1 commit
-
-
Jedidiah authored
-
- 01 Aug, 2017 1 commit
-
-
Tim Zallmann authored
-
- 06 Apr, 2017 2 commits
-
-
Jose Ivan Vargas authored
-
Jose Ivan Vargas authored
-
- 31 Dec, 2016 1 commit
-
-
Kushal Pandya authored
-
- 07 Nov, 2016 1 commit
-
-
winniehell authored
-
- 18 Aug, 2016 2 commits
-
-
Timothy Andrew authored
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.
-
Timothy Andrew authored
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).
-
- 16 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 429cd5e57fb1.
-
James Lopez authored
-
- 15 Jun, 2016 1 commit
-
-
Timothy Andrew authored
- Also change the help message to indicate that an authenticator app is now a prerequisite for U2F.
-
- 06 Jun, 2016 1 commit
-
-
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
-