- 14 Jul, 2016 1 commit
-
-
Timothy Andrew authored
1. According to the spec, either we have a single challenge with a number of `signRequests`, or a number of `signRequests`, each with it's own challenge. 2. Previously, we had both these - per-request challenges, as well as a single extra challenge. 3. This commit changes this so that the per-request challenges are removed, leaving only a single challenge, as per the v1.1 U2F API. 4. The existing implementation didn't work in Firefox, because the Firefox (extension) implementation is less flexible with regard to the inputs. 5. Fix teaspoon specs. 6. References: https://fidoalliance.org/specs/fido-u2f-v1.0-nfc-bt-amendment-20150514/fido-u2f-javascript-api.html#h2_background
-
- 12 Jul, 2016 4 commits
-
-
tiagonbotelho authored
-
tiagonbotelho authored
-
tiagonbotelho authored
-
tiagonbotelho authored
-
- 11 Jul, 2016 1 commit
-
-
tiagonbotelho authored
-
- 08 Jul, 2016 1 commit
-
-
tiagonbotelho authored
-
- 30 Jun, 2016 1 commit
-
-
winniehell authored
-
- 23 Jun, 2016 1 commit
-
-
Connor Shea authored
-
- 20 Jun, 2016 2 commits
-
-
Phil Hughes authored
-
Phil Hughes authored
-
- 16 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 13e37a3e.
-
James Lopez authored
-
- 15 Jun, 2016 3 commits
-
-
Fatih Acet authored
-
Rémy Coutable authored
Without this sane default you would get the following error when you tried to instantiate a new MergeRequest object with no argument (i.e. `new MergeRequest();`): TypeError: undefined is not an object (evaluating 'this.opts.action') Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Timothy Andrew authored
- We added a `current_user.two_factor_via_otp?` check to the view. When rendering the view via the teaspoon fixture, `current_user` is `nil`.
-
- 09 Jun, 2016 2 commits
-
-
Fatih Acet authored
-
Fatih Acet authored
-
- 07 Jun, 2016 1 commit
-
-
Fatih Acet authored
-
- 06 Jun, 2016 4 commits
-
-
Fatih Acet authored
-
Fatih Acet authored
-
Timothy Andrew authored
- Move the `authenticate_with_two_factor` method from `ApplicationController` to the `AuthenticatesWithTwoFactor` module, where it should be.
-
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
-
- 05 Jun, 2016 1 commit
-
-
Phil Hughes authored
CHANGELOG item
-
- 03 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- 02 Jun, 2016 2 commits
-
-
Connor Shea authored
-
Connor Shea authored
-
- 20 May, 2016 1 commit
-
-
Alfredo Sumaran authored
-
- 11 May, 2016 1 commit
-
-
Fatih Acet authored
-
- 08 May, 2016 1 commit
-
-
Benedikt Huss authored
-
- 04 May, 2016 2 commits
-
-
Benedikt Huss authored
-
Benedikt Huss authored
-
- 14 Apr, 2016 1 commit
-
-
Phil Hughes authored
Updated JS spec to include gl_form
-
- 12 Apr, 2016 2 commits
-
-
Phil Hughes authored
-
Phil Hughes authored
-
- 05 Apr, 2016 1 commit
-
-
Annabel Dunstone authored
-
- 04 Apr, 2016 1 commit
-
-
Phil Hughes authored
-
- 02 Mar, 2016 1 commit
-
-
Robert Speicher authored
Now it will work on any field inside that form, and it's easier to scope new behavior, which is what we're adding next!
-
- 05 Feb, 2016 1 commit
-
-
Phil Hughes authored
-