Add an alternative captcha provider to reCAPTCHA
Problem to solve
Currently GitLab only supports reCAPTCHA as a captcha provider.
This ticket propose adding the ability to have an alternative (one or many) captcha provider that is configurable by the user (they aren't forced to use reCAPTCHA only).
Intended users
Tagging people who might be interested in this: @alexbuijs, @smcgivern, @nick.thomas
Further details
Mostly covered in the discussion here: #21998
Proposal
User journey: Single User Experience.
- User goes to admin area > reporting.
- They'd see an other to select either reCAPTCHA or the new captcha provider.
I think hCaptcha is a good alternative:
- Privacy Focused (supports privacy pass protocol here)
- Powered by open decentralized protocol and with partially open sourced client.
- Drop-in replacement for reCAPTCHA (minimal changes for this implementation).
Proposed UI (mockup):
Permissions and Security
N/A
Testing
No additional testing needed to the ones we already have in place for reCAPTCHA.
What does success look like, and how can we measure that?
Users being able to choose another captcha provider than reCAPTCHA.
What is the type of buyer?
N/A
Links / references
Related issues: #21998
Edited by M. Hasbini