How to Integrate PallyCon Multi-DRM with Bitmovin Video Player

• EME WTF? An introduction to Encrypted Media Extensions : https://web.dev/eme-basics
• Protecting Audio Content with PallyCon Multi-DRM part 1 : https://pallycon.com/blog/article/protecting-audio-content-with-pallycon-multi-drm-part-1/
• Protecting Audio Content with PallyCon Multi-DRM part 2 : https://pallycon.com/blog/article/protecting-audio-content-with-pallycon-multi-drm-part-2/

• Step 1: Sign up for PallyCon and Bitmovin trial accounts
• Step 2: DRM content packaging with PallyCon CLI Packager
• Step 3: DRM content playback on Bitmovin Player via PallyCon license token integration

2-1.Download and install PallyCon CLI Packager

Download PallyCon CLI Packager from Packager and Sample Downloads page on PallyCon Developer Guide site. Create a folder on a test PC or server to perform the content packaging. And copy the CLI executable file located in ‘bin’ folder of the downloaded zip file. (e.g. ~/pallycon-test/PallyConPackager)

PallyCon CLI Packager supports 64bit Windows and Linux(Ubuntu, CentOS) OS. Gcc and g++ libraries (6.0 or later) are required for Linux OS.

2-2. Package plain MP4 video to MPEG-DASH content

Copy an MP4(H264 AVC) video file for the test to the same folder as the PallyCon CLI Packager executable. You can use the PallyCon introduction video linked below if you want.

PallyCon introduction video : https://pallycon.com/docs/files/pallycon-intro.mp4
PallyCon CLI Packager supports DASH-CENC (Widevine, PlayReady) and HLS-AES (FairPlay) packaging for multi-DRM, as well as NCG and NCG-HLS packaging functions for Netsync Content Guard (NCG) DRM. In this tutorial, we will only proceed with DASH-CENC packaging for a brief test.

Run the command as below to perform a DASH content packaging. Please refer to the below table for the details about each parameters.
./PallyConPackager --site_id --access_key --content_id --dash -i -o

the details about each parameters

Parameter	Input value	Specification	Example
--site_id	The trial site ID which is shown on ‘Integration Settings’ page of PallyCon Console site.	Four uppercase alphanumeric characters	ABCD
--access_key	The access key string which is shown on ‘Integration Settings’ page of PallyCon Console site.	32-length characters	H24FS8wdo3C7CWrSjcIhPYWpYaFu6Lh3
--content_id	Unique ID of content to distinguish each content when DRM packaging and licensing. The DRM encryption key and license are managed based on the ID, and the content ID managed by the CMS (Content Management System) is generally input.	Max 200 alphanumeric characters	pallycon-intro
-i	The name of the original MP4 file to be packaged. If the package is in a different path from the executable file, enter the file name including the path.	Path of a file	~/pallycon-test/input/pallycon-intro.mp4
-o	The path of output folder	Path of a folder	~/pallycon-test/output/pallycon-intro/

parameter: –site_id Input value: The trial site ID which is shown on ‘Integration Settings’ page of PallyCon Console site. Specification: Four uppercase alphanumeric characters Example: ABCD

parameter: –access_key Input value: The access key string which is shown on ‘Integration Settings’ page of PallyCon Console site. Specification: 32-length characters Example: H24FS8wdo3C7CWrSjcIhPYWpYaFu6Lh3

parameter: –content_id Input value: Unique ID of content to distinguish each content when DRM packaging and licensing. The DRM encryption key and license are managed based on the ID, and the content ID managed by the CMS (Content Management System) is generally input. Specification: Max 200 alphanumeric characters Example: pallycon-intro

parameter: -i Input value: The name of the original MP4 file to be packaged. If the package is in a different path from the executable file, enter the file name including the path. Specification: Path of a file Example: ~/pallycon-test/input/pallycon-intro.mp4

parameter: -o Input value: The path of output folder Specification: Path of a folder Example: ~/pallycon-test/output/pallycon-intro/

Edit the ‘bitmovin-player-samplepage.html’ file that you downloaded with a text editor. If you search the string ‘.mpd’ with the search function first, you will go to the following part.

var source = {
dash: 'https://bitmovin-a.akamaihd.net/content/MI201109210084_1/mpds/f08e80da-bf1d-4e3d-8899-f0f6155f6efa.mpd',
hls: 'https://bitmovin-a.akamaihd.net/content/MI201109210084_1/m3u8s/f08e80da-bf1d-4e3d-8899-f0f6155f6efa.m3u8',
progressive: 'https://bitmovin-a.akamaihd.net/content/MI201109210084_1/MI201109210084_mpeg-4_hd_high_1080p25_10mbits.mp4',
poster: 'https://bitmovin-a.akamaihd.net/content/MI201109210084_1/poster.jpg'
};


Modify the contents of the above source to fit the test environment as shown below.


var source = {
dash: 'https://test-web-server-url/pallycon-intro/dash/stream.mpd',
drm: {
widevine: {
LA_URL: "https://license.pallycon.com/ri/licenseManager.do",
headers: {
"pallycon-customdata-v2" : "CUSTOM_HEADER_VALUE"
}
},
playready: {
LA_URL: "https://license.pallycon.com/ri/licenseManager.do",
headers: {
"pallycon-customdata-v2" : "CUSTOM_HEADER_VALUE"
}
}
}
};


• The mpd file URL in the above source code should be replaced with the URL that corresponds to the DASH content uploaded to the test web server in Step 2.
• The value of “CUSTOM_HEADER_VALUE” should be replaced with the value of the license token generated later in the process below.

3-2. Create and set the token for DRM license acquisition

In order to play the packaged content, the DRM license must be issued to the player through DRM license integration. PallyCon Multi DRM supports callback and token type licensing, and in this tutorial we will proceed with token licensing.

For detailed instructions on how to issue licenses, please refer to the online guide linked below.

• DRM license integration guide: https://pallycon.com/docs/en/multidrm/license/

The token used in the license request must be generated in accordance with the specifications in the server side (backend) of the video service to which PallyCon Multi-DRM will be applied. In this tutorial, you will use the ‘Create token’ function provided on the ‘Developer Console’ page of the PallyCon site for quick testing. Go to the Developer Console page at the link below and enter the below items on the form.

• ‘Create token’ test page: https://sample.pallycon.com/

Item	Input value	Specification	Example
SITE ID	The trial site ID which is shown on ‘Integration Settings’ page of PallyCon Console site.	Four uppercase alphabet characters	ABCD
SITE Key	The site key string which is shown on ‘Integration Settings’ page of PallyCon Console site.	32-length characters	3H24FS8wdo3C7CWrSjcIhPYWpYaFu6Lh
ACCESS Key	The access key string which is shown on ‘Integration Settings’ page of PallyCon Console site.	32-length characters	gktt7xArRiSrWXEvrommuBdUD6Ktk3cP
DRM Type	The name of DRM which is supported by client web browser	widevine/playready/fairplay	Chrome/FireFox: widevine, IE11/Edge: playready
CID	The content ID which was input to CLI packager in Step 2.	Max 200 alphanumeric characters	pallycon-intro
USER ID	A unique user ID used to verify the rights of the content service user. In the token-based license integration, a token must be generated after the authorization check is completed between the content service backend and the client.	Max 200 alphanumeric characters	test-user
Time stamp	The validity time of the token. Generally, it is set as token generation time, and the token is valid for 600 seconds after that point by default. The length of validity can be configured on PallyCon Console site.	yyyy-mm-ddThh:mm:ssZ (GMT based)	2019-04-03T08:30:00Z
Token Rule	DRM-related rule data to be applied when issuing license (refer to Token guide for details)	JSON string	{ "playback_policy": { "limit": true, "persistent": false, "duration" : 300 } }

Item: USER ID Input value: A unique user ID used to verify the rights of the content service user. In the token-based license integration, a token must be generated after the authorization check is completed between the content service backend and the client. Specification: Max 200 alphanumeric characters Example: test-user

Item: Token Rule Input value: DRM-related rule data to be applied when issuing license (refer to Token guide for details) Specification: JSON string Example: { "playback_policy": { "limit": true, "persistent": false, "duration" : 300 } }

Item: Time stamp Input value: The validity time of the token. Generally, it is set as token generation time, and the token is valid for 600 seconds after that point by default. The length of validity can be configured on PallyCon Console site. Specification: yyyy-mm-ddThh:mm:ssZ(GMT based) Example: 2019-04-03T08:30:00Z

Item: SITE Key Input value: The site key string which is shown on ‘Integration Settings’ page of PallyCon Console site. Specification: 32-length characters Example: 3H24FS8wdo3C7CWrSjcIhPYWpYaFu6Lh

Item: SITE ID Input value: The trial site ID which is shown on ‘Integration Settings’ page of PallyCon Console site. Specification: Four uppercase alphabet characters Example: ABCD

Item: DRM Type Input value: The name of DRM which is supported by client web browser Specification: widevine/playready/Fairplay Example: Chrome/FireFox: widevine, IE11/Edge: playready

Item: CID Input value: The content ID which was input to CLI packager in Step 2. Specification: Max 200 alphanumeric characters Example: pallycon-intro

Item: ACCESS Key Input value: The access key string which is shown on ‘Integration Settings’ page of PallyCon Console site. Specification: 32-length characters Example: gktt7xArRiSrWXEvrommuBdUD6Ktk3cP

Enter the values required to generate the token as above and click the ‘REQUEST TOKEN’ button. A token string will be created at the bottom of the page. Copy the string and paste it into ‘CUSTOM_HEADER_VALUE’ for each DRM in the Bitmovin player sample file you modified in step 3-2. The final html source will be as below.
var source = {
dash: 'https://test-web-server-url/pallycon-intro/dash/stream.mpd',
drm: {
widevine: {
LA_URL: "https://license.pallycon.com/ri/licenseManager.do",
headers: {
"pallycon-customdata-v2" : "eyJ0aW1lc3RhbXAiOiIyMDE5LTA0LTAzVDA5OjA4OjAwWiIsImhhc2giOiJRTEUzOGxPQjVJUzZ3cUlYOSt6eWpUR1oxOXVrXC9BVVdFQkxkSjRQZVNiaz0iLCJ0b2tlbiI6IkhCOHVvRXBaTTZ2dEFIVXFLSTQyM0s0amNHTzltU1A5YjJWM2IzaTNEd21cL3dpS1wvSlV2WTVWVVQ4WVNZTUVLZm5PXC9PXC9yTU9hUlZrR0JuQXI0RStSM1FFUVJZandldlNRaGN2cWR6QWN6THFcL1VhaXhRK1J5Z21EMnRDWDFXdFwvdmQ5d1JpeWd4RFgyckt6VWwxeUZyUT09Iiwic2l0ZV9pZCI6IjE3WUwiLCJkcm1fdHlwZSI6IndpZGV2aW5lIiwidXNlcl9pZCI6InRlc3QtdXNlciIsImNpZCI6InBhbGx5Y29uLWludHJvIn0="
}
},
playready: {
LA_URL: "https://license.pallycon.com/ri/licenseManager.do",
headers: {
"pallycon-customdata-v2" : "eyJ0aW1lc3RhbXAiOiIyMDE5LTA0LTAzVDA5OjA4OjAwWiIsImhhc2giOiI2S0t6dVY2NWFwSnpDSmJxdDRhK1NRUjZJM0ZFRlB4amdJaHNCc3g4OXNJPSIsInRva2VuIjoiSEI4dW9FcFpNNnZ0QUhVcUtJNDIzSzRqY0dPOW1TUDliMlYzYjNpM0R3bVwvd2lLXC9KVXZZNVZVVDhZU1lNRUtmbk9cL09cL3JNT2FSVmtHQm5BcjRFK1IzUUVRUllqd2V2U1FoY3ZxZHpBY3pMcVwvVWFpeFErUnlnbUQydENYMVd0XC92ZDl3Uml5Z3hEWDJyS3pVbDF5RnJRPT0iLCJzaXRlX2lkIjoiMTdZTCIsImRybV90eXBlIjoicGxheXJlYWR5IiwidXNlcl9pZCI6InRlc3QtdXNlciIsImNpZCI6InBhbGx5Y29uLWludHJvIn0="
}
}
}
};


• The token string in the sample code above should be replaced with the value you created yourself through the tutorial.
• To test playback on both Chrome / Firefox (Widevine DRM) and IE11 / Edge (PlayReady DRM), you need to create and set two different tokens with the ‘DRM Type’ input as ‘widevine’ and ‘playready’.

3-3. Upload modified player sample and test playback

Upload the player sample html file that you set up to the license token string to the test web server. Browse to the sample html page’s URL using a multi-DRM supported web browser such as Chrome, Firefox, IE11, and Edge. The Bitmovin Video Player sample page will be displayed as below.