tileradotorg/synapse
1
0
Fork 0
forked from MirrorHub/synapse
Code Pull requests Activity

Fix notes about well-known and acme (#5357)

Browse source 
fixes #4951
This commit is contained in:
Richard van der Hoff 2019-06-05 15:12:33 +01:00 committed by GitHub
parent d53faa40e9
commit 95ab2eb4a1
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
changelog.d/5357.doc Normal file
View file

@ -0,0 +1 @@
Fix notes about ACME in the MSC1711 faq.

11
docs/MSC1711_certificates_FAQ.md
View file

@ -145,12 +145,11 @@ You can do this with a `.well-known` file as follows:
1. Keep the SRV record in place - it is needed for backwards compatibility 1. Keep the SRV record in place - it is needed for backwards compatibility
with Synapse 0.34 and earlier. with Synapse 0.34 and earlier.
2. Give synapse a certificate corresponding to the target domain 2. Give Synapse a certificate corresponding to the target domain
(`customer.example.net` in the above example). Currently Synapse's ACME (`customer.example.net` in the above example). You can either use Synapse's
support [does not support built-in [ACME support](./ACME.md) for this (via the `domain` parameter in
this](https://github.com/matrix-org/synapse/issues/4552), so you will have the `acme` section), or acquire a certificate yourself and give it to
to acquire a certificate yourself and give it to Synapse via Synapse via `tls_certificate_path` and `tls_private_key_path`.
`tls_certificate_path` and `tls_private_key_path`.
3. Restart Synapse to ensure the new certificate is loaded. 3. Restart Synapse to ensure the new certificate is loaded.