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: token, and token proxy type. Please refer to the table below for the differences and advantages and disadvantages of the methods.
|Token||The user authentication is done between your back-end system and client app before generating a license token.||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.|
|Token proxy||A proxy server of the customer’s backend relays the license request/response between the client application and the PallyCon license server.||Additional security can be implemented at the customer’s discretion during the license issuance process. Functions such as limiting the number of devices can be implemented through custom type DRM license data.||Higher difficulty because of many parts that the customer needs to implement.|
The old callback type integration method is deprecated because delays or errors may occur depending on the situation of the customer’s system. We recommend the use of token method in general, and the token proxy can be used to implement DRM integration at the customer’s discretion, such as additional security processing.
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 document describes how to create a license token with step-by-step example codes.Read More
FPS Cert Registration Tutorial
This document describes the certificate registration process required to integrate FairPlay DRM.Read More