delta/gitlab/gitlab-ce.git/spec/features/login_spec.rb, branch trigger-docs gitlab.com: gitlab-org/gitlab-ce.git fixes part1 of files to start using active tense 2016-08-09T14:06:23+00:00 tiagonbotelho tiagonbotelho@hotmail.com 2016-07-25T18:16:19+00:00 519275c1102ad8a1d56f5807de2d8a1ae4b21dc0 






Remove provider path, replace with dynamic path.
2016-08-03T17:50:38+00:00

Connor Shea
connor.james.shea@gmail.com

2016-07-25T17:40:40+00:00

602fe111912bac119e752b0dfa3b4b3cd81585ff












Added a lot of stubbing to make sure OAUth requests are handled properly with 2FA
2016-07-07T21:54:03+00:00

Patricio Cano
suprnova32@gmail.com

2016-07-05T21:34:34+00:00

2a0be666e3078e28a02de298b386ec4c09232978












Change order of stubbing to fix tests
2016-07-04T16:50:11+00:00

Patricio Cano
suprnova32@gmail.com

2016-07-04T16:50:11+00:00

40e16b22f9a4ecb7dd7a25c4a0355809bed70ebe












Added tests for 2FA check on OAuth request
2016-07-04T16:00:34+00:00

Patricio Cano
suprnova32@gmail.com

2016-06-30T19:54:07+00:00

5467260528018774c8baec65f3cbf692bb3d93b7












Implement authentication (login) using a U2F device.
2016-06-06T07:20:31+00:00

Timothy Andrew
mail@timothyandrew.net

2016-06-06T04:50:39+00:00

86b07caa599a7f064e9077770b1a87c670d7607c

- Move the `authenticate_with_two_factor` method from
  `ApplicationController` to the `AuthenticatesWithTwoFactor` module,
  where it should be.





- Move the `authenticate_with_two_factor` method from
  `ApplicationController` to the `AuthenticatesWithTwoFactor` module,
  where it should be.







Merge branch 'upgrade-devise-two-factor' into 'master'

2016-06-02T00:44:41+00:00

Robert Speicher
robert@gitlab.com

2016-06-02T00:44:41+00:00

7d33fba7af94667311ab9a7d7d7041ed72ba3937


Upgrade devise, devise-two-factor, and attr_encrypted

Devise 4 includes support for Rails 5, working towards #14286. devise-async doesn't support Devise 4.0 and in 4.1 the bug that was blocking using Devise's built-in ActiveJob integration was fixed. So devise-async is removed. devise-two-factor 3.0.0 is required for Devise 4 support.

attr_encrypted and encryptor are optional but recommended upgrades for devise-two-factor 3.0.0. The mode and algorithm will need to be changed in order to update to attr_encrypted 4.x in the future.

See merge request !4216





Upgrade devise, devise-two-factor, and attr_encrypted

Devise 4 includes support for Rails 5, working towards #14286. devise-async doesn't support Devise 4.0 and in 4.1 the bug that was blocking using Devise's built-in ActiveJob integration was fixed. So devise-async is removed. devise-two-factor 3.0.0 is required for Devise 4 support.

attr_encrypted and encryptor are optional but recommended upgrades for devise-two-factor 3.0.0. The mode and algorithm will need to be changed in order to update to attr_encrypted 4.x in the future.

See merge request !4216






Pass the "Remember me" value to the 2FA token form
2016-05-31T02:25:35+00:00

Robert Speicher
rspeicher@gmail.com

2016-05-31T02:17:26+00:00

a602df303175aaaf1d5b60a2c009f5e259d187db

Prior, if a user had 2FA enabled and checked the "Remember me" field,
the setting was ignored because the OTP input was on a new form and the
value was never passed.

Closes #18000





Prior, if a user had 2FA enabled and checked the "Remember me" field,
the setting was ignored because the OTP input was on a new form and the
value was never passed.

Closes #18000







Upgrade attr_encrypted and encryptor
2016-05-30T19:51:21+00:00

Connor Shea
connor.james.shea@gmail.com

2016-05-19T18:55:25+00:00

d287315dbf1a1493e3f2c2511e559204cc914ff8

attr_encrypted (1.3.4 => 3.0.1) Changelog:
https://github.com/attr-encrypted/attr_encrypted/blob/master/CHANGELOG.m
d

attr_encrypted 2.x included a vulnerability, so that major version is
skipped. 3.x requires that the algorithm and mode used by each
encrypted attribute is specified explicitly.

`nil` is no longer a valid value for the encrypted_value_iv field, so
it’s changed to a randomly generated string.





attr_encrypted (1.3.4 => 3.0.1) Changelog:
https://github.com/attr-encrypted/attr_encrypted/blob/master/CHANGELOG.m
d

attr_encrypted 2.x included a vulnerability, so that major version is
skipped. 3.x requires that the algorithm and mode used by each
encrypted attribute is specified explicitly.

`nil` is no longer a valid value for the encrypted_value_iv field, so
it’s changed to a randomly generated string.







Fix a spec that was failing due to !3483
2016-05-04T10:17:12+00:00

Rémy Coutable
remy@rymai.me

2016-05-04T10:17:12+00:00

5f89c9642e6fa48d0487e40ea2dc6977676855dc

Spec were skipped in this MR so that tests started to fail in master
instead of in this MR!

Signed-off-by: Rémy Coutable <remy@rymai.me>





Spec were skipped in this MR so that tests started to fail in master
instead of in this MR!

Signed-off-by: Rémy Coutable <remy@rymai.me>