about summary refs log tree commit diff
path: root/spec/controllers/settings/two_factor_authentication/confirmations_controller_spec.rb
AgeCommit message (Collapse)Author
2019-09-18Add password challenge to 2FA settings, e-mail notifications (#11878)Eugen Rochko
Fix #3961
2019-09-18Fix TOTP codes not being filtered from logs during enabling/disabling (#11877)Eugen Rochko
Not a serious issue because they are meaningless past single use
2019-08-30Fix uncaught parameter missing exceptions and missing error templates (#11702)Eugen Rochko
2018-10-04Lint pass (#8876)aus-social
2018-04-21Use raw status code on have_http_status (#7214)Yamagishi Kazutoshi
2018-01-21Redirect to 2FA creation page when otp_secret is not available (#6314)Aboobacker MK
2017-05-29Cover Settings::TwoFactorAuthentication::ConfirmationsController more (#3386)Akihiko Odaki
2017-04-222FA controller cleanup (#2296)Matt Jankowski
* Add spec coverage for settings/two_factor_auth area * extract setup method for qr code * Move otp required check to before action * Merge method only used once * Remove duplicate view * Consolidate creation of @codes for backup * Move settings/2fq#recovery_codes to settings/recovery_codes#create * Rename settings/two_factor_auth#disable to #destroy * Add coverage for the otp required path on 2fa#show * Clean up the recovery codes list styles * Move settings/two_factor_auth to settings/two_factor_authentication * Reorganize the settings two factor auth area Updated to use a flow like: - settings/two_factor_authentication goes to a #show view which has a button either enable or disable 2fa on the account - the disable button turns off the otp requirement for the user - the enable button cycles the user secret and redirects to a confirmation page - the confirmation page is a #new view which shows the QR code for user - that page posts to #create which verifies the code, and creates the recovery codes - that create action shares a view with a recovery codes controller which can be used separately to reset codes if needed