2019-09-17 14:55:29 +03:00
|
|
|
# Overview
|
2015-03-30 20:27:42 +03:00
|
|
|
Captcha can be enabled for this home server. This file explains how to do that.
|
2015-03-30 20:18:19 +03:00
|
|
|
The captcha mechanism used is Google's ReCaptcha. This requires API keys from Google.
|
|
|
|
|
2019-09-17 14:55:29 +03:00
|
|
|
## Getting keys
|
|
|
|
|
2019-10-30 15:30:20 +03:00
|
|
|
Requires a site/secret key pair from:
|
2015-03-30 20:18:19 +03:00
|
|
|
|
2019-09-17 14:55:29 +03:00
|
|
|
<https://developers.google.com/recaptcha/>
|
2015-03-30 20:18:19 +03:00
|
|
|
|
2019-05-29 06:04:24 +03:00
|
|
|
Must be a reCAPTCHA v2 key using the "I'm not a robot" Checkbox option
|
2015-03-30 20:18:19 +03:00
|
|
|
|
2019-09-17 14:55:29 +03:00
|
|
|
## Setting ReCaptcha Keys
|
|
|
|
|
2016-12-01 15:01:54 +03:00
|
|
|
The keys are a config option on the home server config. If they are not
|
2019-09-17 14:55:29 +03:00
|
|
|
visible, you can generate them via `--generate-config`. Set the following value:
|
|
|
|
|
2019-10-30 15:30:20 +03:00
|
|
|
recaptcha_public_key: YOUR_SITE_KEY
|
|
|
|
recaptcha_private_key: YOUR_SECRET_KEY
|
2015-03-30 20:18:19 +03:00
|
|
|
|
2019-09-17 14:55:29 +03:00
|
|
|
In addition, you MUST enable captchas via:
|
2016-12-01 15:01:54 +03:00
|
|
|
|
2019-09-17 14:55:29 +03:00
|
|
|
enable_registration_captcha: true
|
2015-03-30 20:18:19 +03:00
|
|
|
|
2019-09-17 14:55:29 +03:00
|
|
|
## Configuring IP used for auth
|
2015-03-30 20:18:19 +03:00
|
|
|
|
|
|
|
The ReCaptcha API requires that the IP address of the user who solved the
|
|
|
|
captcha is sent. If the client is connecting through a proxy or load balancer,
|
2019-09-17 14:55:29 +03:00
|
|
|
it may be required to use the `X-Forwarded-For` (XFF) header instead of the origin
|
|
|
|
IP address. This can be configured using the `x_forwarded` directive in the
|
2017-02-09 08:21:02 +03:00
|
|
|
listeners section of the homeserver.yaml configuration file.
|