From 691008d14ba89080c2355834ed338f10b39b26e8 Mon Sep 17 00:00:00 2001 From: Mateusz Konieczny Date: Fri, 8 Feb 2019 16:35:24 +0000 Subject: Update what supports U2F workflow note that "only" and "so we _strongly_ recommend" is becoming suspect. It may be considered worthwhile to change it, but in turn it would fail to explain why GitLab requires that both methods are enabled --- doc/user/profile/account/two_factor_authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/profile/account/two_factor_authentication.md b/doc/user/profile/account/two_factor_authentication.md index 83bc79925e1..0a7c5832a2d 100644 --- a/doc/user/profile/account/two_factor_authentication.md +++ b/doc/user/profile/account/two_factor_authentication.md @@ -18,7 +18,7 @@ the second factor of authentication. Once enabled, in addition to supplying your password to login, you'll be prompted to activate your U2F device (usually by pressing a button on it), and it will perform secure authentication on your behalf. -The U2F workflow is only supported by Google Chrome at this point, so we _strongly_ recommend +The U2F workflow is only [supported by](https://caniuse.com/#search=U2F) Google Chrome, Opera and Firefox at this point, so we _strongly_ recommend that you set up both methods of two-factor authentication, so you can still access your account from other browsers. -- cgit v1.2.1