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.
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.
Backlot’s publishing rules are also a prerequisite part of Rights Locker.
- 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
For a step-by-step process to configure this requirement, see Ooyala Player Token.
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.