Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: allow passing Livekit token via query parameters #288

Open
grrtrr opened this issue Aug 7, 2023 · 0 comments
Open

[Feature Request]: allow passing Livekit token via query parameters #288

grrtrr opened this issue Aug 7, 2023 · 0 comments

Comments

@grrtrr
Copy link

grrtrr commented Aug 7, 2023

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:

  1. via the Authorization header, and
  2. via URL query parameters.

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:

  1. passing the LiveKit token via Authorization header (as currently done, perhaps as fallback); or alternatively
  2. passing the LiveKit token via URL query parameters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant