DRM License Issuance Integration
To play the packaged content on a client device, you must acquire a DRM license from that device. Licensing can be done in two ways: callback and token. Please refer to the table below for the differences and advantages and disadvantages of the two methods.
||The major implementation is between PallyCon license server and your back-end system.
||Smaller implementation work on the client side. Better control of license issuance and security
||License acquisition may take longer than token model due to the additional communication via callback.
||The major implementation is between your back-end system and client apps.
||Better performance on license issuance because the process is simpler than callback type.
||More implementation work needed in client app. You need to manage the generated token securely on your own.
The below documents describe how to issue DRM licenses, such as callback and token methods.
License Callback Guide
In the license callback scenario, the callback page URL registered for each service site is called by PallyCon cloud server for authentication when a client requests a license. This document describes how to issue a license using callback.
License Token Guide
In the license token scenario, the service site generates a license token of a predefined specification and delivers it to the client, and the client acquires DRM license using the token. This document describes how to issue a token-based license.
License Token Tutorial
This tutorial explains how to create a license token by the above specification. This document has step-by-step guide with sample code.
Multi-DRM License Integration
Customers have an option to integrate PallyCon multi-DRM with native DRM client on their own, without using PallyCon client SDKs. This document explains how to integrate multi-DRM license issuance without the SDKs.
License Error Code
This document describes various error codes that may occur during the DRM license issuance process.