- 18 Aug, 2016 1 commit
-
-
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).
-
- 14 Jul, 2016 2 commits
-
-
Timothy Andrew authored
1. This scenario was previously tested for the registration flow, but not authentication.
-
Timothy Andrew authored
1. Only on supported Chrome versions 2. Mainly, this lets us simplify the javascript-based U2F check to `window.u2f`, where `window.u2f` can either be loaded from the GitLab server (for Chrome) or from the Firefox extension. 3. This is a better way to provide browser detection for U2F.
-
- 11 Jul, 2016 1 commit
-
-
Connor Shea authored
-
- 30 Jun, 2016 1 commit
-
-
Connor Shea authored
-
- 16 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 13e37a3e.
-
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
-