You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can be reviewed commit by commit
There are a few improvements over the experimental support:
- authorisation of Synapse <-> MAS requests is simplified, with a single
shared secret, removing the need for provisioning a client on the MAS
side
- the tests actually spawn a real server, allowing us to test the rust
introspection layer
- we now check that the device advertised in introspection actually
exist, making it so that when a user logs out, the tokens are
immediately invalidated, even if the cache doesn't expire
- it doesn't rely on discovery anymore, rather on a static endpoint
base. This means users don't have to override the introspection endpoint
to avoid internet roundtrips
- it doesn't depend on `authlib` anymore, as we simplified a lot the
calls done from Synapse to MAS
We still have to update the MAS documentation about the Synapse setup,
but that can be done later.
---------
Co-authored-by: reivilibre <[email protected]>
Copy file name to clipboardExpand all lines: docs/upgrade.md
+25-3Lines changed: 25 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,7 +164,29 @@ The Grafana dashboard JSON in `contrib/grafana/synapse.json` has been updated to
164
164
this change but you will need to manually update your own existing Grafana dashboards
165
165
using these metrics.
166
166
167
+
## Stable integration with Matrix Authentication Service
167
168
169
+
Support for [Matrix Authentication Service (MAS)](https://github.com/element-hq/matrix-authentication-service) is now stable, with a simplified configuration.
170
+
This stable integration requires MAS 0.20.0 or later.
171
+
172
+
The existing `experimental_features.msc3861` configuration option is now deprecated and will be removed in Synapse v1.137.0.
173
+
174
+
Synapse deployments already using MAS should now use the new configuration options:
175
+
176
+
```yaml
177
+
matrix_authentication_service:
178
+
# Enable the MAS integration
179
+
enabled: true
180
+
# The base URL where Synapse will contact MAS
181
+
endpoint: http://localhost:8080
182
+
# The shared secret used to authenticate MAS requests, must be the same as `matrix.secret` in the MAS configuration
183
+
# See https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#matrix
184
+
secret: "asecurerandomsecretstring"
185
+
```
186
+
187
+
They must remove the `experimental_features.msc3861` configuration option from their configuration.
188
+
189
+
They can also remove the client previously used by Synapse [in the MAS configuration](https://element-hq.github.io/matrix-authentication-service/reference/configuration.html#clients) as it is no longer in use.
168
190
169
191
# Upgrading to v1.135.0
170
192
@@ -186,10 +208,10 @@ native ICU library on your system is no longer required.
186
208
## Documented endpoint which can be delegated to a federation worker
187
209
188
210
The endpoint `^/_matrix/federation/v1/version$` can be delegated to a federation
189
-
worker. This is not new behaviour, but had not been documented yet. The
190
-
[list of delegatable endpoints](workers.md#synapseappgeneric_worker) has
211
+
worker. This is not new behaviour, but had not been documented yet. The
212
+
[list of delegatable endpoints](workers.md#synapseappgeneric_worker) has
191
213
been updated to include it. Make sure to check your reverse proxy rules if you
Copy file name to clipboardExpand all lines: docs/usage/configuration/config_documentation.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -643,6 +643,28 @@ no_proxy_hosts:
643
643
- 172.30.0.0/16
644
644
```
645
645
---
646
+
### `matrix_authentication_service`
647
+
648
+
*(object)* The `matrix_authentication_service` setting configures integration with [Matrix Authentication Service (MAS)](https://github.com/element-hq/matrix-authentication-service).
649
+
650
+
This setting has the following sub-options:
651
+
652
+
* `enabled` (boolean): Whether or not to enable the MAS integration. If this is set to `false`, Synapse will use its legacy internal authentication API. Defaults to `false`.
653
+
654
+
* `endpoint` (string): The URL where Synapse can reach MAS. This *must* have the `discovery` and `oauth` resources mounted. Defaults to `"http://localhost:8080"`.
655
+
656
+
* `secret` (string|null): A shared secret that will be used to authenticate requests from and to MAS.
657
+
658
+
* `secret_path` (string|null): Alternative to `secret`, reading the shared secret from a file. The file should be a plain text file, containing only the secret. Synapse reads the secret from the given file once at startup.
659
+
660
+
Example configuration:
661
+
```yaml
662
+
matrix_authentication_service:
663
+
enabled: true
664
+
secret: someverysecuresecret
665
+
endpoint: http://localhost:8080
666
+
```
667
+
---
646
668
### `dummy_events_threshold`
647
669
648
670
*(integer)* Forward extremities can build up in a room due to networking delays between homeservers. Once this happens in a large room, calculation of the state of that room can become quite expensive. To mitigate this, once the number of forward extremities reaches a given threshold, Synapse will send an `org.matrix.dummy_event` event, which will reduce the forward extremities in the room.
0 commit comments