|
|
|
|
@ -309,6 +309,10 @@ limit_remote_rooms:
|
|
|
|
|
#
|
|
|
|
|
#complexity_error: "This room is too complex."
|
|
|
|
|
|
|
|
|
|
# allow server admins to join complex rooms. Default is false.
|
|
|
|
|
#
|
|
|
|
|
#admins_can_join: true
|
|
|
|
|
|
|
|
|
|
# Whether to require a user to be in the room to add an alias to it.
|
|
|
|
|
# Defaults to 'true'.
|
|
|
|
|
#
|
|
|
|
|
@ -703,6 +707,10 @@ log_config: "/data/{{ matrix_server_fqn_matrix }}.log.config"
|
|
|
|
|
# - one for ratelimiting redactions by room admins. If this is not explicitly
|
|
|
|
|
# set then it uses the same ratelimiting as per rc_message. This is useful
|
|
|
|
|
# to allow room admins to deal with abuse quickly.
|
|
|
|
|
# - two for ratelimiting number of rooms a user can join, "local" for when
|
|
|
|
|
# users are joining rooms the server is already in (this is cheap) vs
|
|
|
|
|
# "remote" for when users are trying to join rooms not on the server (which
|
|
|
|
|
# can be more expensive)
|
|
|
|
|
#
|
|
|
|
|
# The defaults are as shown below.
|
|
|
|
|
#
|
|
|
|
|
@ -731,6 +739,14 @@ rc_login: {{ matrix_synapse_rc_login|to_json }}
|
|
|
|
|
#rc_admin_redaction:
|
|
|
|
|
# per_second: 1
|
|
|
|
|
# burst_count: 50
|
|
|
|
|
#
|
|
|
|
|
#rc_joins:
|
|
|
|
|
# local:
|
|
|
|
|
# per_second: 0.1
|
|
|
|
|
# burst_count: 3
|
|
|
|
|
# remote:
|
|
|
|
|
# per_second: 0.01
|
|
|
|
|
# burst_count: 3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Ratelimiting settings for incoming federation
|
|
|
|
|
@ -1117,25 +1133,6 @@ allow_guest_access: {{ matrix_synapse_allow_guest_access|to_json }}
|
|
|
|
|
#
|
|
|
|
|
#default_identity_server: https://matrix.org
|
|
|
|
|
|
|
|
|
|
# The list of identity servers trusted to verify third party
|
|
|
|
|
# identifiers by this server.
|
|
|
|
|
#
|
|
|
|
|
# Also defines the ID server which will be called when an account is
|
|
|
|
|
# deactivated (one will be picked arbitrarily).
|
|
|
|
|
#
|
|
|
|
|
# Note: This option is deprecated. Since v0.99.4, Synapse has tracked which identity
|
|
|
|
|
# server a 3PID has been bound to. For 3PIDs bound before then, Synapse runs a
|
|
|
|
|
# background migration script, informing itself that the identity server all of its
|
|
|
|
|
# 3PIDs have been bound to is likely one of the below.
|
|
|
|
|
#
|
|
|
|
|
# As of Synapse v1.4.0, all other functionality of this option has been deprecated, and
|
|
|
|
|
# it is now solely used for the purposes of the background migration script, and can be
|
|
|
|
|
# removed once it has run.
|
|
|
|
|
{% if matrix_synapse_trusted_third_party_id_servers|length > 0 %}
|
|
|
|
|
trusted_third_party_id_servers:
|
|
|
|
|
{{ matrix_synapse_trusted_third_party_id_servers|to_nice_yaml }}
|
|
|
|
|
{% endif %}
|
|
|
|
|
|
|
|
|
|
# Handle threepid (email/phone etc) registration and password resets through a set of
|
|
|
|
|
# *trusted* identity servers. Note that this allows the configured identity server to
|
|
|
|
|
# reset passwords for accounts!
|
|
|
|
|
@ -1546,6 +1543,17 @@ saml2_config:
|
|
|
|
|
#
|
|
|
|
|
#grandfathered_mxid_source_attribute: upn
|
|
|
|
|
|
|
|
|
|
# It is possible to configure Synapse to only allow logins if SAML attributes
|
|
|
|
|
# match particular values. The requirements can be listed under
|
|
|
|
|
# `attribute_requirements` as shown below. All of the listed attributes must
|
|
|
|
|
# match for the login to be permitted.
|
|
|
|
|
#
|
|
|
|
|
#attribute_requirements:
|
|
|
|
|
# - attribute: userGroup
|
|
|
|
|
# value: "staff"
|
|
|
|
|
# - attribute: department
|
|
|
|
|
# value: "sales"
|
|
|
|
|
|
|
|
|
|
# Directory in which Synapse will try to find the template files below.
|
|
|
|
|
# If not set, default templates from within the Synapse package will be used.
|
|
|
|
|
#
|
|
|
|
|
|
Slavi Pantaleev
4 years ago