From d18dcbc6958a18a475d49b9dc178b6395a9d6bbf Mon Sep 17 00:00:00 2001 From: Michal Nowierski Date: Sun, 18 Feb 2024 14:07:31 +0100 Subject: [PATCH] Changes proposed to fix issue (#1280) * Changes proposed to fix issue https://github.com/SeleniumHQ/seleniumhq.github.io/issues/1279 * Update two_factor_authentication.en.md update [deploy site] --- .../test_practices/discouraged/two_factor_authentication.en.md | 1 + 1 file changed, 1 insertion(+) diff --git a/website_and_docs/content/documentation/test_practices/discouraged/two_factor_authentication.en.md b/website_and_docs/content/documentation/test_practices/discouraged/two_factor_authentication.en.md index 7504f4789c4..ebbc483b926 100644 --- a/website_and_docs/content/documentation/test_practices/discouraged/two_factor_authentication.en.md +++ b/website_and_docs/content/documentation/test_practices/discouraged/two_factor_authentication.en.md @@ -18,6 +18,7 @@ Selenium tests and not as secure. So, you should avoid automating 2FA. There are few options to get around 2FA checks: +* If you want the functionality to still be tested, one option is to ask your team to create a "special token" that will work in test environment. That won't require usage of a mobile device, and will ensure the test journey is covered. * Disable 2FA for certain Users in the test environment, so that you can use those user credentials in the automation. * Disable 2FA in your test environment.