diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-13 15:09:18 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-13 15:09:18 +0300 |
| commit | ce34395e91c28f282eeff3792caee84438ebb8a0 (patch) | |
| tree | d350d2bf057e6707d11727701312580b8389bfed /doc/integration/recaptcha.md | |
| parent | 778ea71394b9bc20b614f766fbb90ddd7ef0cfe9 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/integration/recaptcha.md')
| -rw-r--r-- | doc/integration/recaptcha.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/integration/recaptcha.md b/doc/integration/recaptcha.md index bf2e6568ea6..48c83f1393b 100644 --- a/doc/integration/recaptcha.md +++ b/doc/integration/recaptcha.md @@ -15,6 +15,12 @@ To use reCAPTCHA, first you must create a site and private key. 1. Fill all reCAPTCHA fields with keys from previous steps. 1. Check the `Enable reCAPTCHA` checkbox. 1. Save the configuration. +1. Change the first line of the `#execute` method in `app/services/spam/spam_verdict_service.rb` + to `return CONDITONAL_ALLOW` so that the spam check short-circuits and triggers the response to + return `recaptcha_html`. + +NOTE: **Note:** +Make sure you are viewing an issuable in a project that is public, and if you're working with an issue, the issue is public. ## Enabling reCAPTCHA for user logins via passwords |