Add support for Google reCAPTCHA in user registration to prevent spammers
Merge request reports
Activity
/cc: @dblessing
mentioned in issue omnibus-gitlab#1014 (closed)
@stanhu Thanks for this. For now let's keep these settings in gitlab.yml. That way we can get this introduced in a patch sooner than later. We can come back and add application settings, if necessary.
I created a corresponding issue in
omnibus-gitlab
so we can add config there once this is merged.Let me know if/how I can help. I believe @sytses would like to get this on GitLab.com as soon as possible.
@dblessing I agree.
@dblessing I believe it's ready to go. Apparently it's not possible to restyle the reCAPTCHA block, so I'm punting that:
http://stackoverflow.com/questions/27713505/recaptcha-api-v2-styling
Added 1 commit:
- 9e0f532f - Add documentation for using reCAPTCHA
We may also need to consider how we can better use this to prevent spammers on GitLab.com. For example, a spammer may create an account by hand and then use a script to create issues via the API. This wouldn't help that.
Edited by Stan Hu@stanhu The nice thing is that deleting the users will delete all created issues via the API.
@dzaporozhets can we get this shipped ASAP?
346 346 # cas3: 347 347 # session_duration: 28800 348 348 349 # reCAPTCHA settings. See: http://www.google.com/recaptcha 350 recaptcha: 351 enabled: false 352 public_key: 'YOUR_PUBLIC_KEY' 353 private_key: 'YOUR_PRIVATE_KEY' @marin can you please make sure this setting are included in omnibus?
@dzaporozhets Thanks, created https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1019 for that.
mentioned in commit 202010e3
Thanks @stanhu and @dzaporozhets
@rspeicher please ship in patch release
@stanhu Why is
Put settings in application_settings
crossed out, why did you decide against adding the settings there?@marin I didn't have time to add it and didn't push on it given the comments above.