cqrenet/matrix-docker-ansible-deploy
3
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2026-04-09 02:15:37 +00:00
Code Issues Wiki Activity

Synapse Admin is Ketesa now! (#5113)

Browse Source 
* Synapse Admin is Ketesa now!

* i18n changes

* add automatic migration

* fix migration version in vars

* add a note about routing for OIDC Auth

* mention v1.0.0 announcement blog post

* Update docs/container-images.md

Co-authored-by: Suguru Hirahara <luixxiul@users.noreply.github.com>

* Update CHANGELOG.md

Co-authored-by: Suguru Hirahara <luixxiul@users.noreply.github.com>

---------

Co-authored-by: Suguru Hirahara <luixxiul@users.noreply.github.com>
This commit is contained in:
Aine
2026-04-03 15:26:18 +01:00
committed by GitHub
parent 3d40026f93
commit 9049a82945
100 changed files with 19316 additions and 15130 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/configuring-playbook-matrix-authentication-service.md
View File

@@ -51,7 +51,7 @@ This section details what you can expect when switching to the Matrix Authentica
- ❌ **Synapse password providers will need to be disabled**. You can no longer use [shared-secret-auth](./configuring-playbook-shared-secret-auth.md), [rest-auth](./configuring-playbook-rest-auth.md), [LDAP auth](./configuring-playbook-ldap-auth.md), etc. When the authentication flow is handled by MAS (not by Synapse anymore), it doesn't make sense to extend the Synapse authentication flow with additional modules. Many bridges used to rely on shared-secret-auth for doing double-puppeting (impersonating other users), but most (at least the mautrix bridges) nowadays use [Appservice Double Puppet](./configuring-playbook-appservice-double-puppet.md) as a better alternative. Older/maintained bridges may still rely on shared-secret-auth, as do other services like [matrix-corporal](./configuring-playbook-matrix-corporal.md).
- ❌ Certain **tools like [Synapse Admin](./configuring-playbook-synapse-admin.md) do not have full compatibility with MAS yet**. Synapse Admin already supports OIDC auth, browsing users (which Synapse will internally fetch from MAS) and updating user avatars. However, editing users (passwords, etc.) now needs to happen directly against MAS using the [MAS Admin API](https://element-hq.github.io/matrix-authentication-service/api/index.html), which Synapse Admin cannot interact with yet. You may be interested in using [Element Admin](./configuring-playbook-element-admin.md) for these purposes.
- ✅ **[Ketesa](./configuring-playbook-ketesa.md) has full MAS integration**. Ketesa supports OIDC auth, user management, all session types (browser, OAuth2, compatibility), linked email addresses, upstream OAuth provider links, MAS policy data, and user creation through MAS. It is the recommended tool for managing homeservers running MAS.
- ❌ **Some services experience issues when authenticating via MAS**: