I packaged DRM content using the DoveRunner CLI packager or a third-party packager. How can I verify whether the packaging was completed successfully?
If the packaging output is generated without any errors during the DRM packaging process, you can verify the Content ID (CID) and the packaging date and time in the DoveRunner ContentSecurity Console.
Since DRM-packaged DASH/HLS content has encrypted media files, playback is not possible on players without DRM integration. To test DRM content playback, a player integrated with DoveRunner Multi-DRM is required. The easiest way to perform a test is to use the ContentSecurity Developer Console and its Web Player playback test page.
Alternatively, you can use DRM test pages provided by third-party player vendors or build and test your own playback page using the DoveRunner HTML5 Player sample .
Prepare content URLs for testing
Upload the DRM-packaged DASH/HLS content files to an origin server that supports TLS-based HTTPS URLs, and prepare the URL of the MPD or M3U8 file. (For example, a public object URL in an Amazon S3 bucket.)
If the content is stored in a local environment instead of a remote server, DRM playback testing is restricted. For basic content security, an HTTPS URL that supports certificate-based encrypted communication is required. (Chrome browser requirement)
In addition, to play the content using the test player in the ContentSecurity Developer Console, you must allow devconsole.doverunner.com as an allowed origin on your origin server or CDN to prevent CORS errors. For details on CORS configuration, please contact your CDN or server infrastructure provider.
Check packaging information and account information
Log in to the DoveRunner Console and verify the following information. These values are required to generate a license token in the next step.
- Content ID (CID): Check the CID of the corresponding packaging entry on the “DRM Packaging History” page under the “Multi-DRM” menu.
- Site ID, Site Key, Access Key: Available on the “DRM Settings” page.
Since the console does not display the original file name or stream details used for packaging, customers must manage the mapping between content and CID separately when performing multiple packaging operations.
Generate a test license token
To obtain a license required for DRM content playback, a license token must be generated. In a production environment, license tokens must be generated in real time by the customer’s backend server. However, for simple playback testing, a test token can be generated using the Developer Console.
Access the License Token Generator page in the ContentSecurity Developer Console and enter the following information.
- SITE ID, SITE Key, ACCESS Key, CID: Enter the values verified in the previous step.
-
DRM Type: Select the DRM type according to the web browser used for testing.
- Chrome, Firefox: Widevine
- Edge (Windows): PlayReady
- Safari: FairPlay -
USER ID: Enter any arbitrary user ID string (for example,
test-user). - Time stamp: Leave blank to apply the current time.
-
Response Format, Key Rotation: Keep the default values (
original,false). -
License Policy JSON: Keep the default value
{"policy_version":2}to apply the basic license policy.
After entering the information above, click the “Generate Token” button to create the license token.
Playback using the test player
Go to the Web Player playback test page in the ContentSecurity Developer Console and enter the following information.
- License URL: Keep the default value.
- DASH URL (Edge, Chrome, Firefox): Enter the MPD URL of the packaged content.
- HLS URL (Safari): Enter the main M3U8 URL of the packaged content.
- FPS Cert URL (Safari): Enter the certificate URL after registering the FPS certificate. Refer to FPS Certificate Registration.
- pallycon-customdata-v2: Enter the license token string generated in the previous step.
After entering all required information, click the “PLAY” button to verify license issuance and playback of the DRM-packaged content. If a license or playback error occurs, verify that all preparation steps were completed correctly before contacting the Help Center.