DRM License Issuance

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.

Integration type
Description Pros Cons
Callback 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.
Token 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 callback type integration method is not recommended because delays or errors may occur depending on the situation of the customer’s system. Please use the token method instead, and contact us if you want the callback method for a specific reason.

The below documents describe how to issue DRM licenses.

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.

Read More

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.

Read More

FPS Cert Registration Tutorial

This document describes the certificate registration process required to integrate FairPlay DRM.

Read More

License Error Code

This document describes various error codes that may occur during the DRM license issuance process.

Read More