mirrors/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2024-11-22 09:35:45 +03:00
Code Issues Projects Releases Packages Wiki Activity
synapse/docs/CAPTCHA_SETUP.rst
Daniel Dent fdbd90e25d Update CAPTCHA_SETUP.rst X-Forwarded-For docs 
It looks like CAPTCHA_SETUP.rst contains information relevant to an old version of Synapse, but Synapse now has a different approach to configuring use of the X-Forwarded-For header.
2017-02-08 21:21:02 -08:00

1 KiB
Raw Blame History

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 using the x_forwarded directive in the listeners section of the homeserver.yaml configuration file.