PlayReady Workflow

The PlayReady Workflow describes the process needed to implement and initialize PlayReady content protection.

If you want to use PlayReady, you need to:
  • Implement PlayReady in accordance with the device specific SDKs that you are using to create your custom players. You pre-configure your device SDK and PlayReady set up according to the SDK instructions.

  • Initialize PlayReady and the device SDK in the SDK-specific language (this will vary from device to device). Set up your app in accordance with the applicable platform programming guide.

  • You will make a call the Authorization API (this is a JSON RESTFUL API call).
  • You will make a PlayReady license request that included the auth token from the authorization API.

To use PlayReady for DRM-protection of Smooth streaming, work with your Ooyala Customer Success Manager or professional services to enable PlayReady support. With the implementation of PlayReady DRM, each content viewer needs an individual license as the content is encrypted and is useless without a license.

The following two diagrams illustrate how PlayReady is related to the Ooyala Player Token (an optional but recommended user authentication feature) and the Ooyala Authorization API that handles the user authentication requests.

Note: Ooyala Player Token is available only if your Ooyala account includes this functionality. To enable Ooyala Player Token, contact your account manager.

The following diagram shows how the player authenticates the user using the Ooyala Player Token.

The following diagram shows the continuation of the workflow showing the fetching of the PlayReady license.

The following table describes in greater detail the workflow steps, illustrated in the prior diagrams, that are necessary for using PlayReady for content protection. Your app needs to perform the following workflow:

Step Activity Responsible Party Additional Documentation
1 The video player app, authenticates the user against the content provider and requests an Ooyala Player Token (OPT). App developers and content provider’s services Ooyala Player Token Guide
2 The content (identity) provider supplies an Ooyala Player Token to the video player app that indicates the authentication status of the user. App developers and content provider’s services Ooyala Player Token Guide
3 The video player app makes an authorization request to Ooyala that includes two key pieces of data:
  • the embed code.

  • the Ooyala Player Token.

App developers Ooyala Player Token Guide and Authorization API Guide
4 The video manifest is fetched using the stream URL. The response contains the stream URL for the video (this will be the manifest when using smooth streaming). App developers Authorization API Guide
5 The PlayReady license is requested using the acquisition URL from the manifest. The auth_token must be included within the license request. App developers  
6 Ooyala provides the license to playback DRM content. Ooyala