Warn loudly about encrypted appservices being unsupported

This commit is contained in:
Quentin Gliech
2024-02-07 17:02:58 +01:00
parent 04966fd9b6
commit 39955e03f3
3 changed files with 12 additions and 0 deletions

View File

@@ -17,6 +17,7 @@ You can learn more about Matrix and OIDC at [areweoidcyet.com](https://areweoidc
- Authentication methods:
- ✅ Upstream OIDC
- 🚧 Local password
- ‼️ [Application Services login](https://matrix-org.github.io/matrix-authentication-service/as-login.html) (**Encrypted bridges**)
- Migration support
- ✅ Compatibility layer for legacy Matrix authentication
- ✅ Advisor on migration readiness

View File

@@ -33,3 +33,7 @@
- [Contributing](./development/contributing.md)
- [Architecture](./development/architecture.md)
- [Database](./development/database.md)
---
[Application Services login](./as-login.md)

7
docs/as-login.md Normal file
View File

@@ -0,0 +1,7 @@
# About Application Services login
Encrypted Application Services/Bridges currently leverage the `m.login.application_service` login type to create devices for users.
This API is *not* available in the Matrix Authentication Service.
We're working on a solution to support this use case, but in the meantime, this means **encrypted bridges will work with the Matrix Authentication Service.**
A workaround is to disable E2EE support in your bridge setup.