[SDK] Describe the transport auth flows in the architecture document

How a LiveKit transport is authenticated with by shape and role, the server name on connections and the options that now take a Transport.

(cherry picked from commit 26d9e1b0ae1e1f1ba8c3689bd50ba2e34aa0e820)
This commit is contained in:
Timo K.
2026-10-13 13:00:58 +02:00
parent 4aa249daf5
commit 7e4e260273
2 changed files with 62 additions and 23 deletions
+1 -1
View File
@@ -33,7 +33,7 @@ Element Call still imports the LiveKit packages in a few places. Each is a gap i
the SDK's API rather than something to rename: the import goes away when the SDK
grows the piece. The names Element Call owes to the outside stay as they are: the
`livekit.livekit_service_url` key in `config.json`, the persisted setting keys
`extended-livekit-logs` and `custom-livekit-url`, the Posthog fields
`extended-livekit-logs` and `custom-transport`, the Posthog fields
`callBackend` and `callReconnectingCountLivekit`, the rageshake field
`call_backend`, and the translated error strings.