diff options
author | Erik Johnston <erik@matrix.org> | 2015-05-06 13:48:06 +0100 |
---|---|---|
committer | Erik Johnston <erik@matrix.org> | 2015-05-06 13:48:06 +0100 |
commit | 938939fd89518ba6db833c9463973f18d752fefc (patch) | |
tree | d7f809cdbd009daacb0b5f750f284d6ccd8b5645 /docs | |
parent | Linkify docs/postgres.sql (diff) | |
download | synapse-938939fd89518ba6db833c9463973f18d752fefc.tar.xz |
Move CAPTCHA_SETUP to docs/
Diffstat (limited to 'docs')
-rw-r--r-- | docs/CAPTCHA_SETUP | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/docs/CAPTCHA_SETUP b/docs/CAPTCHA_SETUP new file mode 100644 index 0000000000..75ff80981b --- /dev/null +++ b/docs/CAPTCHA_SETUP @@ -0,0 +1,31 @@ +Captcha can be enabled for this home server. This file explains how to do that. +The captcha mechanism used is Google's ReCaptcha. This requires API keys from Google. + +Getting keys +------------ +Requires a public/private key pair from: + +https://developers.google.com/recaptcha/ + + +Setting ReCaptcha Keys +---------------------- +The keys are a config option on the home server config. If they are not +visible, you can generate them via --generate-config. Set the following value: + + recaptcha_public_key: YOUR_PUBLIC_KEY + recaptcha_private_key: YOUR_PRIVATE_KEY + +In addition, you MUST enable captchas via: + + enable_registration_captcha: true + +Configuring IP used for auth +---------------------------- +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, +it may be required to use the X-Forwarded-For (XFF) header instead of the origin +IP address. This can be configured as an option on the home server like so: + + captcha_ip_origin_is_x_forwarded: true + |