Configurable CORS credentials (#456)

* Configurable CORS credentials

* update readme
This commit is contained in:
Aine
2025-04-05 18:08:29 +00:00
committed by GitHub
parent f4084969b6
commit 218f0ba03c
7 changed files with 62 additions and 0 deletions

View File

@@ -27,6 +27,7 @@
* [Configuration](#configuration)
* [Prefilling login form](#prefilling-login-form)
* [Restricting available homeserver](#restricting-available-homeserver)
* [Configuring CORS credentials](#configuring-cors-credentials)
* [Protecting appservice managed users](#protecting-appservice-managed-users)
* [Adding custom menu items](#adding-custom-menu-items)
* [Usage](#usage)
@@ -111,6 +112,7 @@ The following changes are already implemented:
* [Respect base url (`BASE_PATH` / `vite build --base`) when loading `config.json`](https://github.com/etkecc/synapse-admin/pull/274)
* [Add Users' Account Data tab](https://github.com/etkecc/synapse-admin/pull/276)
* [Make bulk registration CSV import more user-friendly](https://github.com/etkecc/synapse-admin/pull/411)
* [Configurable CORS Credentials](https://github.com/etkecc/synapse-admin/pull/456)
#### exclusive for [etke.cc](https://etke.cc) customers
@@ -180,6 +182,12 @@ You can restrict the homeserver(s), so that the user can no longer define it him
[Documentation](./docs/restrict-hs.md)
### Configuring CORS credentials
You can configure the CORS credentials mode for the Synapse Admin instance.
[Documentation](./docs/cors-credentials.md)
### Protecting appservice managed users
To avoid accidental adjustments of appservice-managed users (e.g., puppets created by a bridge) and breaking the bridge,