HTML5 Player Integration Guide

Overview

This document explains how to play streaming content (DASH or HLS) protected with multi-DRM (PlayReady, Widevine, FairPlay Streaming) using the HTML5 player from the web page of the service site.

  1. MPEG-DASH CENC content
  • DASH streaming content protected by PlayReady and Widevine DRM encrypted under the Common Encryption standard. Depending on your browser, PlayReady (IE11, Edge) or Widevine (Chrome, FireFox) DRM is applied.
  1. HLS FPS(FairPlay Streaming) content
  • HTTP Live Streaming content encrypted with Sample AES and protected by FairPlay Streaming. Applies to Safari browsers running on Mac OS X (10.10 or later).

In order to issue multi-DRM licenses in HTML5 player, user authentication must be performed through the integration with PallyCon cloud and customer service site. Please check Multi-DRM Native Integration for license issuance integration.

Sample codes

We share DRM integration sample code for various HTML5 players through Github service. Demo content and integration data are included in the sample code, so you can check the playback of DRM content without any modification other than the license key of the commercial player.

Go to the sample repository

Basic integration method

To integrate HTML5 Player with PallyCon Multi DRM service, you need to set the Custom Data or Token for PallyCon license issuance in the Custom HTTP Header through the DRM related API provided by the player.

Widevine / PlayReady settings

Widevine and PlayReady DRM can be configured by setting the license request URL and custom HTTP header as follows. When running in a browser that supports MPEG-DASH CENC, each corresponding DRM setting will be applied to play DASH content.

FairPlay Streaming settings

For FairPlay Streaming integration, additional APIs are used in addition to the license request address and Custom HTTP Header information. To set the CERT file for the FPS deployment package that is issued by Apple, set the certificateURL value and use the prepareContentId and prepareCertificate APIs as described in the code below.

It is possible to integrate players that are not mentioned in this document as long as the player supports EME(Encrypted Media Extension) standard. Please refer to the input value description and sample code to integrate it on your own, or contact for tech support via Helpdesk.

Input Value Description

Please refer to the description below for the input values ​​used in each player-specific API code.

Name
Value Remarks
DASH_MANIFEST_URL (dashUri) Manifest(mpd) URL of MPEG-DASH content which is encrypted by CENC spec common for Widevine and PlayReady
SERVER_CERTIFICATE Certificate data which is issued by Widevine server. Used for CENC with Widevine DRM running on Chrome 58 or later version. If this data is missing, the certificate will be requested to PallyCon Cloud before license acquisition.
PALLYCON_LA_URL (licenseUri) License acquisition URL of PallyCon Cloud. https://license-global.pallycon.com/ri/licenseManager.do Same for all DRM types
CUSTOM_HEADER_NAME Name of Custom HTTP Header which is sent to LA URL with license request. use pallycon-customdata-v2
CUSTOM_HEADER_VALUE License token or auth data for proxy integration
HLS_PLAYLIST_URL (hlsUri) Manifest(m3u8) file URL of HLS content which is packaged for FairPlay Streaming (FPS) DRM.
PALLYCON_FPS_CERT_URL (fairplayCertUri) URL for FPS certification data. Returns base64 encoded cert data.
https://license-global.pallycon.com/ri/fpsKeyManager.do?siteId='Your_Site_ID'
Input Site_ID which is issued by PallyCon Cloud service. (4byte)
PALLYCON_FPS_CERT_DER_URL (fairplayCertDerUri) URL for FPS cert download. Returns .der cert file.
https://license-global.pallycon.com/ri/fpsCert.do?siteId='Your_Site_ID'
Input Site_ID which is issued by PallyCon Cloud service. (4byte)
You may use one of the FPS certificate URLs (either Base64-encoded data version or certificate file download version) depending on the certificate configuration supported by each player. For details, please refer to the sample code for each player.

Shaka Player Integration

Shaka player is an HTML5 player that supports HLS and MPEG-DASH. It supports CENC content playback via Widevine and PlayReady, and HLS content via FairPlay. For more information about Shaka player, please see the links below.

Please refer to the sample code to configure Shaka player’s API settings for each type of DRM.

Handling Error Response

If the PallyCon cloud encounters an error while processing license request, you can get the error code and message in the player. Shaka player provides registerResponseFilter API for error handling.

Example

player.getNetworkingEngine().registerResponseFilter(function(type, response) {
  // Alias some utilities provided by the library.
  if (type == shaka.net.NetworkingEngine.RequestType.LICENSE) {
    console.log(response.data.byteLength);
    var responseText = arrayBufferToString(response.data);
    console.log("response : " + responseText);
    if (responseText.indexOf('errorCode') > 0) {
      // this alert should be properly parsed and displayed for commercial use
      var errorCode = JSON.parse(responseText).errorCode;
      if("8002" != errorCode){
        alert("PallyCon Error : " + JSON.parse(responseText).message + "(" + JSON.parse(responseText).errorCode+ ")");
      }else{
        var message = JSON.parse(responseText).message;
        alert("Error : " + JSON.parse(message).MESSAGE + "(" + JSON.parse(message).ERROR + ")");
      }
    }
  }
});

registerResponseFilter is applied to both Widevine and PlayReady. When applying to your service site, please use the above example code as reference to deal with errors in a way that is appropriate for the service.

For the list of error codes and corresponding message contents, please refer to the License Error Code page.

Bitmovin Player Integration

Bitmovin player is an HTML5 player that supports HLS and MPEG-DASH. For more information on the Bitmovin player, please refer to the links below.

Please refer to the sample code to configure Bitmovin player’s JSON API settings for each type of DRM.

Handling Error Response

If the PallyCon cloud encounters an error while processing license request, you can get the error code and message in the player. Bitmovin player provides prepareLicense API for error handling.

Example (Widevine)

var conf = {
  ...
  source: {
    dash: 'https://d28giv01x4pn7o.cloudfront.net/tears_of_steel_720p/stream.mpd',
    drm: {
      widevine: {
        LA_URL: 'https://license-global.pallycon.com/ri/licenseManager.do',
        headers: {
          'pallycon-customdata-v2' : 'eyJkYXRhIjoibWJLV1NjSUNIU25WMjZQWFB4cGlDSmNsOHdJMHV1Qlc1cnFqU0hzV1BRSTM4ek1iZTcyZ3Q5TllZRXprRmFjUU5hVU8yRGZUb2l0YzZndXZ5RzJOWlE9PSIsInNpdGVfaWQiOiJERU1PIiwiZHJtX3R5cGUiOiJXaWRldmluZSJ9'
        },
        prepareLicense: function(licenseObj) {
          var license = {
            license: licenseObj.license
          };
          try {
            var pallyconObj = JSON.parse(String.fromCharCode.apply(null, licenseObj.license));
            if (pallyconObj && pallyconObj.errorCode && pallyconObj.message) {
              // this response is error, not valid widevine license
              console.log('ri error code : ' + pallyconObj.errorCode + ', message :', pallyconObj.message);

              var fullErrorMsg;
              if (parseInt(pallyconObj.errorCode) == 8002) {
                // getting the error from callback page
                var errorObj = JSON.parse(pallyconObj.message);
                if (errorObj && errorObj.ERROR && errorObj.MESSAGE) {
                  fullErrorMsg = 'RI errorCode : ' + pallyconObj.errorCode + '\nCallback ERROR: ' + errorObj.ERROR + '\nCallback MESSAGE: ' + errorObj.MESSAGE;
                }
              } else {
                // this error is from PallyCon RI
                fullErrorMsg = 'RI errorCode: ' + pallyconObj.errorCode + '\nRI message: ' + pallyconObj.message;
              }
              alert(fullErrorMsg);
            } 
          } catch (e) {
            // this is valid license
            return license;
          }  
      },
      ...
    }
  }
};

The above example shows the processing for the Widevine license response, and if necessary, apply the same process for the prepareLicense API of the PlayReady and FairPlay Streaming as well. When applying to your service site, please use the above example code as reference to deal with errors in a way that is appropriate for the service.

For the list of error codes and corresponding message contents, please refer to the License error code.

THEOplayer Integration

THEOplayer is a cross-platform video player that supports HLS and MPEG-DASH playback in web, mobile apps, and smart TV environments. DASH CENC content protection via Widevine and PlayReady and HLS content protection through FairPlay Streaming. For more information about THEOplayer, please see the links below.

Please refer to the sample code to configure THEOplayer’s API settings for each type of DRM.

Handling Error Response

If the PallyCon cloud encounters an error while processing license request, you can get the error code and message in the player. THEOplayer provides ‘contentprotectionerror’ Event Listener API for error handling.

Example

player.addEventListener("contentprotectionerror", function(data){
    console.log( "error : " + data.error);
    console.log( "licenseAcquisitionMessage : " + data.licenseAcquisitionMessage );
    console.log( "licenseAcquisitionURL : " + data.licenseAcquisitionURL );
    console.log( "mediaTrackType : " + data.mediaTrackType );
    console.log( "status  : " + data.status );
    console.log( "statusText  : " + data.statusText );
    console.log( "type  : " + data.type );
);

Event Listener is applied to both Widevine and PlayReady. When applying to your service site, please use the above example code as reference to deal with errors in a way that is appropriate for the service.

For the list of error codes and corresponding message contents, please refer to the Error code page.

Radiant Media Player Integration

Radiant Media Player (RMP) is a modern go-everywhere HTML5 video player that can create web, mobile & OTT video apps in a snap. For more information on the VideoJS player, please refer to the links below.

Please refer to the sample code to configure Radiant Media Player API settings for each type of DRM.

JW Player Integration

JW Player is an HTML5 player that supports web, mobile and OTT app development. For more information on the JW player, please refer to the links below.

Please refer to the sample code to configure JW Player API settings for each type of DRM.

VideoJS Player integration

VideoJS player is an HTML5 player that supports HLS and MPEG-DASH. For more information on the VideoJS player, please refer to the links below.

You need to use the following plug-in for multi-DRM integration of VideoJS player.

Please refer to the sample code to configure VideoJS player’s API settings for each type of DRM.

Next