From 269e4a8e7c176b7c1f4a176d2e5dcbcf3f5d53d3 Mon Sep 17 00:00:00 2001 From: richvdh Date: Thu, 5 Aug 2021 18:04:08 +0000 Subject: deploy: 457853100240fc5e015e10a62ecffdd799128b0c --- v1.40/print.html | 53 ++++++++++++++++++++++++----------------------------- 1 file changed, 24 insertions(+), 29 deletions(-) (limited to 'v1.40/print.html') diff --git a/v1.40/print.html b/v1.40/print.html index 3c0a29ccfb..f784e0f0f0 100644 --- a/v1.40/print.html +++ b/v1.40/print.html @@ -1504,9 +1504,9 @@ particular server:

Upgrading to v1.37.0

Deprecation of the current spam checker interface

The current spam checker interface is deprecated in favour of a new generic modules system. -Authors of spam checker modules can refer to this +Authors of spam checker modules can refer to this documentation -to update their modules. Synapse administrators can refer to this +to update their modules. Synapse administrators can refer to this documentation to update their configuration once the modules they are using have been updated.

We plan to remove support for the current spam checker interface in August 2021.

@@ -1559,8 +1559,7 @@ to remove excess writeahead logs in order for Prometheus to recover. Instructions for doing so are provided here.

Dropping support for old Python, Postgres and SQLite versions

-

In line with our deprecation -policy, +

In line with our deprecation policy, we've dropped support for Python 3.5 and PostgreSQL 9.5, as they are no longer supported upstream.

This release of Synapse requires Python 3.6+ and PostgresSQL 9.6+ or @@ -1569,8 +1568,7 @@ SQLite 3.22+.

The deprecated v1 "list accounts" admin API (GET /_synapse/admin/v1/users/<user_id>) has been removed in this version.

-

The v2 list accounts -API +

The v2 list accounts API has been available since Synapse 1.7.0 (2019-12-13), and is accessible under GET /_synapse/admin/v2/users.

The deprecation of the old endpoint was announced with Synapse 1.28.0 @@ -1595,7 +1593,7 @@ that the reverse proxy sets [X-Forwarded-Proto]{.title-ref} header to [https]{.title-ref} or [http]{.title-ref} to indicate the protocol used by the client.

Synapse also requires the [Host]{.title-ref} header to be preserved.

-

See the reverse proxy documentation, where the +

See the reverse proxy documentation, where the example configurations have been updated to show how to set these headers.

(Users of Caddy are unaffected, since we @@ -1610,7 +1608,7 @@ identity providers:

Connect or OAuth2 identity provider, you will need to add [synapse public baseurl]/_synapse/client/oidc/callback to the list of permitted "redirect URIs" at the identity provider.

-

See the OpenID docs for more information on setting +

See the OpenID docs for more information on setting up OpenID Connect.

  • @@ -1779,8 +1777,7 @@ lock down external access to the Admin API endpoints.

    This release deprecates use of the structured: true logging configuration for structured logging. If your logging configuration contains structured: true then it should be modified based on the -structured logging -documentation.

    +structured logging documentation.

    The structured and drains logging options are now deprecated and should be replaced by standard logging configuration of handlers and formatters.

    @@ -1801,13 +1798,12 @@ acts the same as the http_client argument previously passed to ThirdPartyEventRules modules.

    Upgrading to v1.21.0

    Forwarding /_synapse/client through your reverse proxy

    -

    The reverse proxy -documentation +

    The reverse proxy documentation has been updated to include reverse proxy directives for /_synapse/client/* endpoints. As the user password reset flow now uses endpoints under this prefix, you must update your reverse proxy configurations for user password reset to work.

    -

    Additionally, note that the Synapse worker documentation has been updated to

    +

    Additionally, note that the Synapse worker documentation has been updated to

    : state that the /_synapse/client/password_reset/email/submit_token endpoint can be handled

    by all workers. If you make use of Synapse's worker feature, please @@ -1856,7 +1852,7 @@ updated.

    When setting up worker processes, we now recommend the use of a Redis server for replication. The old direct TCP connection method is deprecated and will be removed in a future release. See -workers for more details.

    +workers for more details.

    Upgrading to v1.14.0

    This version includes a database update which is run as part of the upgrade, and which may take a couple of minutes in the case of a large @@ -1969,9 +1965,8 @@ Synapse is running.

    affected. If you are affected, you can run a similar query, omitting the CONCURRENTLY keyword. Note however that this operation may in itself cause Synapse to stop running for some time. -Synapse admins are reminded that SQLite is not recommended for use -outside a test -environment.

    +Synapse admins are reminded that SQLite is not recommended for use +outside a test environment.

  • Once the index has been created, the SELECT query in step 1 above @@ -1988,7 +1983,7 @@ HTTP requests, the temporary index can be removed:

    Upgrading to v1.10.0

    Synapse will now log a warning on start up if used with a PostgreSQL database that has a non-recommended locale set.

    -

    See Postgres for details.

    +

    See Postgres for details.

    Upgrading to v1.8.0

    Specifying a log_file config option will now cause Synapse to refuse to start, and should be replaced by with the log_config option. @@ -2082,8 +2077,8 @@ section headed email, and be sure to have at least the smtp_host, smtp_port and notif_from fields filled out.

    You may also need to set smtp_user, smtp_pass, and require_transport_security.

    -

    See the sample configuration file for more -details on these settings.

    +

    See the sample configuration file +for more details on these settings.

    Delegate email to an identity server

    Some admins will wish to continue using email verification as part of the registration process, but will not immediately have an appropriate @@ -2163,7 +2158,7 @@ for its use in the room directory!

    Upgrading to v1.2.0

    Some counter metrics have been renamed, with the old names deprecated. -See the metrics +See the metrics documentation for details.

    Upgrading to v1.1.0

    @@ -2189,7 +2184,7 @@ more details on upgrading your database.

    Synapse v1.0 is the first release to enforce validation of TLS certificates for the federation API. It is therefore essential that your certificates are correctly configured. See the -FAQ for more information.

    +FAQ for more information.

    Note, v1.0 installations will also no longer be able to federate with servers that have not correctly configured their certificates.

    In rare cases, it may be desirable to disable certificate checking: for @@ -2202,8 +2197,8 @@ ways:-

  • Configure a whitelist of server domains to trust via federation_certificate_verification_whitelist.
    • -

    See the sample configuration file for more -details on these settings.

    +

    See the sample configuration file +for more details on these settings.

    Email

    When a user requests a password reset, Synapse will send an email to the user to confirm the request.

    @@ -2221,8 +2216,8 @@ section headed email, and be sure to have at least the smtp_h

    If you are absolutely certain that you wish to continue using an identity server for password resets, set trust_identity_server_for_password_resets to true.

    -

    See the sample configuration file for more -details on these settings.

    +

    See the sample configuration file +for more details on these settings.

    New email templates

    Some new templates have been added to the default template directory for the purpose of the homeserver sending its own password reset emails. If you have configured a @@ -2237,10 +2232,10 @@ sent to them.

    Upgrading to v0.99.0

    Please be aware that, before Synapse v1.0 is released around March 2019, you will need to replace any self-signed certificates with those -verified by a root CA. Information on how to do so can be found at the -ACME docs.

    +verified by a root CA. Information on how to do so can be found at the +ACME docs.

    For more information on configuring TLS certificates see the -FAQ.

    +FAQ.

    Upgrading to v0.34.0

    1. -- cgit 1.5.1