This document acts as a detailed manual for implementing DRM encryption on a specific stream, beginning with the initial step of transmitting API calls to identify the intended stream for encryption.

Before you start

Kindly undertake the subsequent tasks beforehand:

1. Ensure that the DRM feature is active. Should you require assistance in its configuration, don’t hesitate to reach out to our customer service.
2. Activate HTTPS, which is critical for successful DRM playback. HTTP streams could potentially lead to playback failure.

An example request for encrypting your stream

The example API call facilitates the encryption of the stream https://drmtest-pull.cdnetworks.com/live/dashdrm.mpd.

curl -i --url 'http://ca.haplat.net/wslive/drm/register.action?n=accountId&r=random&k=token' \
-X 'POST' \
-H 'Content-Type: application/json' \
-d '{
    "url": "https://drmtest-pull.cdnetworks.com/live/drmtest.mpd",
    "encryptType": "drm",
    "action": "add",
    "expire": "1682819355"
}'

The request has successfully initiated the encryption of the stream with streamname drmtest, under the application named live. Once encrypted, this DASH stream gains protection from both Widevine and PlayReady. To ascertain whether your stream has been successfully encrypted, examine the HLS or DASH manifest file. In this context, we’ll concentrate on the DASH .mpd file. This manifest file will include a ContentProtection header, containing the essential objects for generating a license challenge. A brief sample is illustrated below:

</ContentProtection>
      <ContentProtection schemeIdUri="urn:uuid:edef8ba9-79d6-4ace-a3c8-27dcd51d21ed">
          <cenc:pssh>AAAAOHBzc2gAAAAA7e+LqXnWSs6jyCfc1R0h7QAAABgSEAnnEHpafEPZng9h+r1lDBZI49yVmwY=</cenc:pssh>
</ContentProtection>

Parameters and Headers

The subsequent headers and parameters are essential for the request:

Request Body

Include the following elements in your request body:

Response Example

{
	"msg": true,
	"code": 200,
	"callTime": "2022-12-07 21:50:16"

}

Error Codes