summaryrefslogtreecommitdiff
path: root/app/controllers/profiles/two_factor_auths_controller.rb
Commit message (Collapse)AuthorAgeFilesLines
* refactor users update serviceJames Lopez2017-09-281-3/+3
|
* refactor services to match EE signatureJames Lopez2017-09-281-3/+3
|
* fix spec failuresJames Lopez2017-06-231-3/+1
|
* update code based on feedbackJames Lopez2017-06-231-1/+3
|
* refactor update user service not to do auth checksJames Lopez2017-06-231-3/+3
|
* more refactoringJames Lopez2017-06-231-2/+1
|
* more refactoring based on feedbackJames Lopez2017-06-231-5/+7
|
* added service in the rest of controllers and classesJames Lopez2017-06-231-3/+3
|
* Add a rubocop rule to check if a method 'redirect_to' is used without ↵31840-add-a-rubocop-that-forbids-redirect_to-inside-a-controller-destroy-action-without-an-explicit-statusblackst0ne2017-06-071-1/+1
| | | | explicitly set 'status' in 'destroy' actions of controllers
* state the reason to the user for the required 2faAlexis Reigel2017-04-061-4/+17
|
* Rename skip_tfa session variable to skip_two_factorMarkus Koller2017-04-061-1/+1
|
* Rename check_2fa_requirement to check_two_factor_requirementMarkus Koller2017-04-061-1/+1
|
* Enable Style/ColonMethodCallDouwe Maan2017-02-231-1/+1
|
* Add GitLab host to 2FA QR and manual infoDrew Blessing2016-12-161-2/+6
| | | | | | | | The two factor authentication account string only had the user's email address. This led to ambiguous entries in two factor code generating apps. This adds the GitLab host to the account string in the standard format (according to Google). No matter the code generator this change disambiguates the entry.
* Address review comments from @smcgivern.17334-u2f-device-identifiersTimothy Andrew2016-08-181-2/+1
| | | | | | | | 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.
* Allow naming U2F devices.Timothy Andrew2016-08-181-3/+8
| | | | | | | | 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).
* Load Javascript U2F library selectively.Timothy Andrew2016-07-141-2/+1
| | | | | | | | | | 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.
* Implement U2F registration.Timothy Andrew2016-06-061-6/+39
| | | | | | | | | | | - 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
* Don't show any "2FA required" message if it's not actually requiredrs-improve-grace-periodRobert Speicher2016-02-291-5/+7
| | | | | | | Prior, if the user had enabled and then disabled 2FA, they would be shown a "You must enable Two-factor Authentication for your account." message when going back to re-activate it, even if 2FA enforcement was disabled.
* Update wording for 2FA requirement noticers-2fa-requirement-wordingRobert Speicher2016-01-231-2/+2
|
* Fixed codestyle and added 2FA documentationfeature/force-tfaGabriel Mazetto2015-12-241-1/+3
|
* specs for forced two-factor authentication and grace periodGabriel Mazetto2015-12-241-1/+8
| | | | simplified code and fixed stuffs
* Grace period support for TFAGabriel Mazetto2015-12-241-1/+13
|
* WIP require two factor authenticationGabriel Mazetto2015-12-241-0/+2
|
* Bump devise-two-factor to 2.0.0rs-bump-two-factorRobert Speicher2015-09-191-1/+1
| | | | | | Addresses internal https://dev.gitlab.org/gitlab/gitlabhq/issues/2605 See https://github.com/tinfoil/devise-two-factor/pull/43
* Add User#disable_two_factor!rs-disable-2faRobert Speicher2015-07-101-7/+1
| | | | | This method encapsulates all the logic for disabling 2FA on a specific User model.
* Use User#two_factor_enabled instead of otp_required_for_loginrs-dev-issue-2415Robert Speicher2015-06-191-2/+2
|
* Prefix 2FA issuer with the GitLab host (e.g., 'dev.gitlab.org')rs-dev-issue-2373Robert Speicher2015-06-161-1/+5
|
* Bump secret key length to 32rs-manual-2fa-entryRobert Speicher2015-05-231-1/+1
|
* Add support for manually entering 2FA detailsRobert Speicher2015-05-231-1/+2
|
* Clear all 2FA-related fields when user disables the featureRobert Speicher2015-05-091-2/+7
|
* Fix nav and layout for TwoFactorAuthsControllerRobert Speicher2015-05-091-1/+1
|
* Render 2fa recovery codes instead of downloading itDmitriy Zaporozhets2015-05-091-3/+3
|
* Add support for backup codesDmitriy Zaporozhets2015-05-091-0/+6
|
* Fix rubocop complainDmitriy Zaporozhets2015-05-091-1/+0
|
* Make 2 factor authentication workDmitriy Zaporozhets2015-05-091-7/+24
|
* Create Two-factor authentication resource for userDmitriy Zaporozhets2015-05-091-0/+22
View Lorry Controller Status