2FA needs to be configured on every login when 2 providers are selected in the configuration

[idziakjakub]

Preconditions and environment

Magento version 2.4.6-p8
2FA enabled for 2 providers: Google Authenticator and U2F (Yubikey and others)

Steps to reproduce

1. Enable 2FA for 2 providers: Google Authenticator and U2F (Yubikey and others) in system configuration
2. Login first time using Google Authenticator authorization
3. Recieve email with link:
   
4. Click the link and scan the QR code in Google Authenticator
5. Log in using the Authenticator code
6. After successful login, log out from the admin
7. Try to log in again
8. Receive an email with a link instead of a form for the Authenticator code

Expected result

After the first login, the next login attempt should show a form with the option to enter an authorization code

Actual result

After the first login, each login attempt sends another email with the need to activate the configuration

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @idziakjakub. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[idziakjakub]

@magento give me 2.4.6-p8 instance

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @idziakjakub,

Thanks for your reporting and collaboration.

We have verified the issue in Latest Magento instance and the issue is not reproducible.Kindly refer the screenshots.

After the first login, the next login attempt was showing a form with the option to enter an authorization code

Could you please check the issue in Latest Magento instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

[idziakjakub]

@magento give me 2.4.6 instance

[engcom-Bravo]

Hi @idziakjakub,

This issue is being closed since it has not been updated in a long time.Please feel free to reopen or raise a new ticket if the issue still exists.

Thanks.