You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is: when the LiveKit server is hosted on premises, third party authorization is required to secure the deployment (TLS termination).
In many cases, this, too, will use an Authorization header.
With the server SDK, this scenario is currently not possible.
What to Do
Make the use of the authentication token configurable to support:
passing the LiveKit token via Authorization header (as currently done, perhaps as fallback); or alternatively
passing the LiveKit token via URL query parameters.
The text was updated successfully, but these errors were encountered:
The use of the
Authorization
header in the SDK rules out using third-party authorization with LiveKit.Problem Description
The current way of attaching a LiveKit token is via an
Authorization
header.There is only one such header, multiple Authorization headers are not supported.
The LiveKit server is flexible in accepting an AccessToken:
Authorization
header, andThe problem is: when the LiveKit server is hosted on premises, third party authorization is required to secure the deployment (TLS termination).
In many cases, this, too, will use an
Authorization
header.With the server SDK, this scenario is currently not possible.
What to Do
Make the use of the authentication token configurable to support:
Authorization
header (as currently done, perhaps as fallback); or alternativelyThe text was updated successfully, but these errors were encountered: