Question/Issue
The server responds with error code 7011 to the DRM license request. When does this error occur and how can I fix it?
Short Description
The 7011 error code occurs when you request a license using an expired token or the time is not come yet. The 'token duration' is used to prevent the license token from being shared and illegally reused. It is a different concept from the 'license duration' of the DRM license itself.
- Token duration: The period of validity from the time of creation (timestamp) of the corresponding token until it is used for issuance of a license (how long you can use the token)
- 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, and the default value is 600 seconds (10 minutes).
Resolution
When the token is expired
To resolve the 7011 error by expired token, you must use a token that was created in real time just before the license request so that the token does not expire. License tokens are basically generated by the customer's content service backend, and the customer must implement a function in the client to receive a new token from the corresponding backend server.
To do this, when the screen that plays the DRM content is loaded, the license token for the content is transmitted and set to the client along with playback-related information such as the content URL. Instead of storing and reusing the received token value, the client should request a new token from the service backend server when necessary.
When the token's timestamp is not come yet
Contrary to the above case, the 7011 error can occur even when the current time is earlier than the timestamp value set in the token. This can happen if the timestamp value is based in a local time zone other than the GMT time zone, or if the time on the system generating the token is incorrect.
First, check that the system time of the server or local environment used for token generation is correct, and then create and enter the timestamp value as the current time based on the GMT time zone.
Precautions
The token validity check may be inconvenient during the integration test process for the introduction of DRM. In this case, you can reduce the hassle of generating a new token every time by setting the token duration arbitrarily long in the DoveRunner Console. (Multi-DRM > DRM Settings > Token Duration)
In this case, there may be a security problem if the token value is leaked. Therefore be sure to set the token validity period below the default value for commercial services.