Backlot Setup

Rights Locker relies on Backlot API calls for creating and managing assets (videos), labels, and publishing rules. In addition, Rights Locker authorization relies on the Ooyala Playback Token. (Available only if your Ooyala account includes Ooyala Player Token. To enable this functionality, contact your account manager.)


Entitlements can be by asset or by label. The Backlot API /v2/labels Backlot API calls create and manage labels. After creating labels and associating them with assets, with Rights Locker you make combinations of labels and publishing rules to define entitlements.

Note: Tip on Label Design: The shallower the hierarchy of labels, the better performance, even though deep “trees” of labels are supported.

Publishing Rules  

Backlot’s publishing rules are also a prerequisite part of Rights Locker.

Note: Rights Locker requires certain properties in publishing rules:
  • The “Require user entitlement” field, require_user_entitlement.
  • The “Require Ooyala Playback Token” container secure_playback_token and its properties

If you have existing publishing rules you want to use with Rights Locker, be sure to update the appropriate rules with these field. See the example PATCH in Extended Example of Rights Locker .

Require Ooyala Playback Token

To ensure that all requests for an asset are subjected to authorization, you need to enable the Ooyala Player Token under PUBLISH tab, Syndication Controls in the Backlot UI, as shown below.

For a step-by-step process to configure this requirement, see Ooyala Player Token for Player V3 (Deprecated).

Programmatically, you can add the secure_playback_token properties to publishing rules to require the token. See the example PATCH in Extended Example of Rights Locker.