In some cases, system integrators need to protect a video asset from being publicly accessible : the asset is played from an intranet, or a form needs to be filled to get access to the video.
...
Tokenisation is activated by Wedia on your DAM instance : please contact your account manager to enable this feature.
Wedia Account Managers have access to this restricted page describing the setup : /wiki/spaces/WD/pages/2055798785Wedia DAM Security rules calculate the conditions to secure an asset : security rules can test a property values, or multiple properties and return a true / false to the DAM, to know if the asset should be secured by a token or not.
In the external website, a special process must be included by web developers / system integrators to generate valid tokens that are appended to the player embed code.
...
Due to the sensible nature of the token generation process, we have no current plan to publish this information publicly.
Time window token validity
Token generated are time-bombed, meaning that they are only valid a certain amount of time.
The duration of the validity is set up during the token generation by the token generation method.
The validity is equal to : start_time + window.
The unit of the timeframe is the second.
The default “window” timespan defaults to 300 seconds, but can be set-up during token generation by setting the window parameter, or using the set_window method.
The default “start time” defaults to the timestamp of the token generation, by can be set up using the set_start_time method.
PHP Sample code
Here is a typical PHP code that will append a valid token to the query string of the player, valid for a time window of 7200 seconds.
Signing function such as “generate_token" are included by the Wedia provided library available in the aforementioned Git repository
...