Magento2: Invisible reCaptcha does not replace default captcha on forgotten password form

[BezV8]

When enabling the invisible recaptcha on 2.3.2 the default magneto recaptcha is not replaced on the forgotten password form and both captchas are presented to the user.

Preconditions (*)

1. Magento 2.3.2
2. v3 reCaptcha enabled on frontend

Steps to reproduce (*)

1. Add api keys for v3 invisible reCaptcha
2. Enable reCaptcha on all front-end pages.

Expected result (*)

1. Default captcha is replaced with the v3 reCaptcha on forgotten password form.

Actual result (*)

1. Both captchas are displayed on form.
   

[m2-assistant[bot]]

Hi @BezV8. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@BezV8 do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[BezV8]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @BezV8. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @BezV8, here is your Magento instance.
Admin access: https://i-24809-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[BezV8]

@magento Can't verify on test instance as it does not seem to have reCaptcha module enabled.

[m2-assistant[bot]]

Hi @shikhamis11. 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: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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.

[shikhamis11]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @shikhamis11. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @shikhamis11, here is your Magento instance.
Admin access: https://i-24809-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

:white_check_mark: Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MC-21433 were created

Issue Available: @shikhamis11, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[Bartlomiejsz]

Hi @shikhamis11, @BezV8, @magento-engcom-team
I wanted to work on this ticket but I believe there is no issue at all. Invisible reCaptcha is not replacement for default captcha, this is just different module. If both are turned on then both appear on frontend, but it is enough to disable default captcha in Stores -> Configuration -> Customers -> Customer Configuration -> CAPTCHA.

Then forgot password form looks like this:

I believe this should be closed.

[m2-assistant[bot]]

Hi @Bartlomiejsz. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [x] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[BezV8]

Hi @shikhamis11, @BezV8, @magento-engcom-team
I wanted to work on this ticket but I believe there is no issue at all. Invisible reCaptcha is not replacement for default captcha, this is just different module. If both are turned on then both appear on frontend, but it is enough to disable default captcha in Stores -> Configuration -> Customers -> Customer Configuration -> CAPTCHA.

Then forgot password form looks like this:

I believe this should be closed.

@Bartlomiejsz If that is the case I think the official magento docs need to be updated. It clearly states in the CE2.3 user guide that

If you have the standard Magento CAPTCHA enabled, reCAPTCHA will override it. You can have both enabled on your Magento instance without issues.

and nowhere in the guide does it say to remove the default captcha. Clearly, either the documentation is incorrect, or the module is not working correctly.

[shikhamis11]

@Bartlomiejsz I agree with @BezV8
in devdocs it is mentioned that If you have the standard Magento CAPTCHA enabled, reCAPTCHA will override it. You can have both enabled on your Magento instance without issues.
It means that only one should be at a time

[magento-engcom-team]

:white_check_mark: Confirmed by @shikhamis11
Thank you for verifying the issue. Based on the provided information internal tickets MC-21458 were created

Issue Available: @shikhamis11, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[vivekkumar945744]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @vivekkumar-webkul. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @vivekkumar-webkul, here is your Magento instance.
Admin access: https://i-24809-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[m2-assistant[bot]]

Hi @gauravagarwal1001. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant[bot]]

Hi @sdzhepa. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• [ ] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [ ] 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[sdzhepa]

FYI: @phoenix128

[sdzhepa]

Hello @BezV8 @gauravagarwal1001
FYI: @shikhamis11

After a couple of internal discussion and clarification with module/functionality owner, I can confirm this is a mistake on DevDocs page.

The two captchas are supposed to be independent implementation. If you enable both of them, you should have them both.

So, it should be fixed in the dev docs

[sdzhepa]

Devdocs has been updated : https://docs.magento.com/user-guide/stores/security-google-recaptcha.html

For the Admin, Google reCAPTCHA can be used on the Sign In page and when a user requests a password reset. If the standard Magento CAPTCHA is also enabled, Google reCAPTCHA can be used at the same time without any problem.