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
We are currently using Web Egress to record a web page which requires passing an access token via an url query parameter for authentication. We observed that the full URL (including the access token) can be retrieved via the Livekit Cloud Egress dashboard.
The access token query parameter is sensitive and should never be logged or stored.
Solution
Introduce a new parameter sensitive_query_params or similar on the WebEgress request API endpoint. This parameter shouldn't be logged or stored and will get appended to the url when starting the Web Egress.
This would allow us to pass the access token query parameter to the web page without having to worry that it will be exposed to users having access to the Livekit cloud dashboard.
The text was updated successfully, but these errors were encountered:
Problem
We are currently using Web Egress to record a web page which requires passing an access token via an url query parameter for authentication. We observed that the full URL (including the access token) can be retrieved via the Livekit Cloud Egress dashboard.
The access token query parameter is sensitive and should never be logged or stored.
Solution
Introduce a new parameter
sensitive_query_params
or similar on the WebEgress request API endpoint. This parameter shouldn't be logged or stored and will get appended to the url when starting the Web Egress.This would allow us to pass the access token query parameter to the web page without having to worry that it will be exposed to users having access to the Livekit cloud dashboard.
The text was updated successfully, but these errors were encountered: