MSC4195: MatrixRTC Transport using LiveKit Backend #4195
Conversation
hughns
changed the title
turt2live
added
voip
proposal
hughns
force-pushed
the
hughns/matrixrtc-livekit
branch
from
054a23c to
6072744
Compare
proposals/4195-matrixrtc-livekit.md
Outdated
|
|
||
| The homeserver restriction could be applied by checking the `matrix_server_name` field of the OpenID token before validating the token. | ||
|
|
||
| The `room_id` could be validated too, and checking that the Matrix user from the OpenID token is a member of the room. |
There was a problem hiding this comment.
From my understanding there's no API that allows room_id validation. Without that implementing access control in a federated environment seems infeasible however.
Given that all members in a session use one SFU via oldest_membership, just validating against matrix_server_name (authenticated using TLS / OpenID) would require allowlisting any server that users might want to join from.
Ideally access control could check either for an allowlisted server or for an existing session with the oldest member being on an allowlisted server, gating an SFU to sessions being started by their "own" users.
There was a problem hiding this comment.
The implementation in element-hq/lk-jwt-service#67 does allow limiting creation of new SFU rooms based on servers in a given allowlist, but still allows arbitrary users to join
github-project-automation
bot
moved this to Tracking for review
in Spec Core Team Workflow
fkwp
changed the title
6 participants
Rendered
Dependencies:
To-do:
POST /sfu/get