- Oct 01, 2020
-
-
BBBSnowball authored
This allows for connecting to certain IdPs, e.g. GitLab.
-
Richard van der Hoff authored
Add a pair of federation metrics to track the delays in sending PDUs to/from particular servers.
-
- Sep 30, 2020
-
-
Patrick Cloke authored
-
- Sep 29, 2020
-
-
Aaron Raimist authored
-
- Sep 28, 2020
-
-
Erik Johnston authored
-
- Sep 25, 2020
-
-
Tdxdxoz authored
Co-authored-by:
Benjamin Koch <bbbsnowball@gmail.com> This adds configuration flags that will match a user to pre-existing users when logging in via OpenID Connect. This is useful when switching to an existing SSO system.
-
- Sep 23, 2020
-
-
Julian Fietkau authored
This change adds a note and a few lines of configuration settings for Apache users to disable ModSecurity for Synapse's virtual hosts. With ModSecurity enabled and running with its default settings, Matrix clients are unable to send chat messages through the Synapse installation. With this change, ModSecurity can be disabled only for the Synapse virtual hosts.
-
- Sep 22, 2020
-
-
Dirk Klimpel authored
Add an admin API to read entries of table `event_reports`. API: `GET /_synapse/admin/v1/event_reports`
-
- Sep 18, 2020
-
-
Dirk Klimpel authored
Add a new admin API `GET /_synapse/admin/v1/users/<user_id>/joined_rooms` to list all rooms where a user is a member.
-
- Sep 14, 2020
-
-
Tulir Asokan authored
-
Patrick Cloke authored
-
- Sep 10, 2020
-
-
Andrew Morgan authored
This PR adds a information about forwarding `/_synapse/client` endpoints through your reverse proxy. The first of these endpoints are introduced in https://github.com/matrix-org/synapse/pull/8004.
-
Andrew Morgan authored
-
Andrew Morgan authored
This PR adds a confirmation step to resetting your user password between clicking the link in your email and your password actually being reset. This is to better align our password reset flow with the industry standard of requiring a confirmation from the user after email validation.
-
- Sep 08, 2020
-
-
Andrew Morgan authored
This is a config option ported over from DINUM's Sydent: https://github.com/matrix-org/sydent/pull/285 They've switched to validating 3PIDs via Synapse rather than Sydent, and would like to retain this functionality. This original purpose for this change is phishing prevention. This solution could also potentially be replaced by a similar one to https://github.com/matrix-org/synapse/pull/8004, but across all `*/submit_token` endpoint. This option may still be useful to enterprise even with that safeguard in place though, if they want to be absolutely sure that their employees don't follow links to other domains.
-
Richard van der Hoff authored
-
- Sep 02, 2020
-
-
Will Hunt authored
* Add shared_rooms api * Add changelog * Add . * Wrap response in {"rooms": } * linting * Add unstable_features key * Remove options from isort that aren't part of 5.x `-y` and `-rc` are now default behaviour and no longer exist. `dont-skip` is no longer required https://timothycrosley.github.io/isort/CHANGELOG/#500-penny-july-4-2020 * Update imports to make isort happy * Add changelog * Update tox.ini file with correct invocation * fix linting again for isort * Vendor prefix unstable API * Fix to match spec * import Codes * import Codes * Use FORBIDDEN * Update changelog.d/7785.feature Co-authored-by:
Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> * Implement get_shared_rooms_for_users * a comma * trailing whitespace * Handle the easy feedback * Switch to using runInteraction * Add tests * Feedback * Seperate unstable endpoint from v2 * Add upgrade node * a line * Fix style by adding a blank line at EOF. * Update synapse/storage/databases/main/user_directory.py Co-authored-by:
Tulir Asokan <tulir@maunium.net> * Update synapse/storage/databases/main/user_directory.py Co-authored-by:
Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> * Update UPGRADE.rst Co-authored-by:
Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> * Fix UPGRADE/CHANGELOG unstable paths unstable unstable unstable Co-authored-by:
Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> Co-authored-by:
Tulir Asokan <tulir@maunium.net> Co-authored-by:
Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> Co-authored-by:
Patrick Cloke <clokep@users.noreply.github.com> Co-authored-by:
Tulir Asokan <tulir@maunium.net>
-
- Sep 01, 2020
-
- Aug 25, 2020
-
-
Andrew Morgan authored
Some fixes to wording I noticed after merging #7377.
-
Andrew Morgan authored
-
Manuel Stahl authored
* Search in columns 'name' and 'displayname' in the admin users endpoint Signed-off-by:
Manuel Stahl <manuel.stahl@awesome-technologies.de>
-
- Aug 24, 2020
-
-
Brendan Abolivier authored
-
- Aug 19, 2020
-
-
Ryan Cole authored
* Updated docs: Added note about missing 308 redirect support. * Added changelog
-
- Aug 18, 2020
-
-
Patrick Cloke authored
-
- Aug 17, 2020
-
- Aug 11, 2020
-
-
Erik Johnston authored
We do this to prevent foot guns. The default config uses a MemoryFilter, but users are free to change to logging to files directly. If they do then they have to ensure to set the `filters: [context]` on the right handler, otherwise records get written with the wrong context. Instead we move the logic to happen when we generate a record, which is when we *log* rather than *handle*. (It's possible to add filters to loggers in the config, however they don't apply to descendant loggers and so they have to be manually set on *every* logger used in the code base)
-
Erik Johnston authored
* Change default log config to buffer by default. This batches up writes to the filesystem, which is more efficient for disk I/O. This means that it can take some time for logs to get written to disk. Note that ERROR logs (and above) immediately flush the buffer. This only effects new installs, as we only write the log config if started with `--generate-config` (in the same way we do for generating signing keys). * Default to keeping last 4 days of logs. This hopefully reduces the amount of logs kept for new servers. Keeping the last 1GB of logs is likely overkill for new servers, but equally may not be enough for busy ones. Instead, we keep the last four days worth of logs, enough so that admins can investigate any problems that happened over e.g. a long weekend.
-
Richard van der Hoff authored
Hopefully this mostly speaks for itself. I also did a bit of cleaning up of the error handling. Fixes #8047
-
- Aug 07, 2020
-
-
Travis Ralston authored
-
Erik Johnston authored
-
- Aug 06, 2020
-
-
Erik Johnston authored
-
- Aug 05, 2020
-
-
Erik Johnston authored
-
- Jul 31, 2020
-
-
Erik Johnston authored
-
Travis Ralston authored
These docs were tested successfully in production by a customer, so it's probably fine.
-
- Jul 30, 2020
-
-
Stuart Mumford authored
-
Erik Johnston authored
-
- Jul 29, 2020
-
-
Erik Johnston authored
-
Aaron Raimist authored
-
- Jul 28, 2020
-
-
Dirk Klimpel authored
Add option ```purge``` to ```POST /_synapse/admin/v1/rooms/<room_id>/delete``` Fixes: #3761 Signed-off-by:
Dirk Klimpel <dirk@klimpel.org>
-
lugino-emeritus authored
Fixes #7901. Signed-off-by:
Niklas Tittjung <nik_t.01@web.de>
-