Question/Issue
I would like to know the relationship and difference between the validity period of the DRM license and the validity period of the license token.
Short Description
The duration of the token used for DRM license request and the duration of the DRM license mainly applied to download scenarios are different concepts, and each has the following meaning.
- Token duration: The validity period from the time of creation of the corresponding token (timestamp) until it is used for a license request (how long the token can be used)
- License duration: The validity period of the DRM license issued by token or callback method (how long the content can be played)
The token duration can be set in the DoveRunner Console for each service site, and the default value is 600 seconds (10 minutes). The license duration is set by the Playback Policy value inside the token. (Duration or expiration date can be specified)
Resolution
When the token expires
If an expired token is used when requesting a license, the error 7011 (Token is Expired.) is returned from the server. In order to prevent this error, a new token should be created and used in real time just before the license request.
In a trial/development environment, you can set an arbitrarily long token duration on the console for testing convenience. In commercial services, it is recommended to set the validity period as short as possible to prevent illegal reuse of token values.
When the license expires
If the license has expired when playing DRM content, a 'License expired' error will occur in the client's DRM module. At this time, in general, the service app checks whether the user wants to extend the license duration. And according to the customer company policy, it can be implemented so that a DRM license with a new validity period is reissued for authorized users.