Use QUANTEEC with a stream secured with tokens

Video streams can be secured with tokens inside the urls. A unique token is generated for every viewer. This token embeds authorizations to watch the stream and information about the video session. Because the urls will be different for every viewer, it is important to inform the QUANTEEC plugin that they are watching the same video.

Identify the videos with a videoID

In the web and native versions of the QUANTEEC plugin, a custom videoID can be inserted inside the QUANTEEC configuration, next to your quanteecKey:

JS

var quanteecConfig = {
    quanteecKey: "<your-quanteec-key>",
    videoID: "<enter-your-custom-videoID>"
};

Java

QuanteecConfig quanteecConfig = new QuanteecConfig("<enter-your-custom-videoID>", "<your-quanteec-key>");
QuanteecCore quanteecCore = new QuanteecExoCore(Context, quanteecConfig); 

Kotlin

val quanteecConfig = QuanteecConfig("<enter-your-custom-videoID>", "<your-quanteec-key>");
val quanteecCore = QuanteecExoCore(context, quanteecConfig); 

The videoID is used by QUANTEEC to identify the video. Hence, two players are able to know they are watching the same content, and they can exchange data. If the videoID is different, the players will not be able to connect. If no videoID is specified in the configuration, the URL of the video source is used as a videoID.

If the video urls are the same for every viewer for one video, then it is enough, and videoID are not needed. However, if specific urls are generated for every viewer (it may be the case if a token is used in the path of the url for security reasons), then the players will think they are not watching the same content, preventing the QUANTEEC plugin from being efficient. In this situation, videoIDs are needed.