This message was deleted.

Hey @polite-kilobyte-67570 , @dry-elephant-14928 do you know how to do that in

meet

or

components-js

? We need to add okta token support which requires to add an Authorization header

what is the flow you are trying to accomplish? Who is the custom header meant for and what will that component do with it?

So basically, we deployed LiveKit server in our cluster which require okta auth for the connection. We made some changes on the server side to support it and we currently deploy our cpp client as a publisher in the cluster within the same network so it has no problem connecting to LiveKit server. But for the reviewer app we need to pass our okta token with Authorization header.

meet

and

components-js

are the two options we have for the browser client. @ancient-minister-81619 feel free to chim in if I miss anything

Hmm.. I'm not following why you'd have to modify anything to make this happen.. that doesn't seem to be the recommended connection model. What we typically recommend is the following: 1. Modify Meet's backend to support Okta via session auth 2. When authenticated, Meet's backend would issue a LiveKit access token (with the right user identity and room) 3. Meet calls backend to issue a token 4. Meet passes access token that to LK server