OpenTV ENTera & OpenTV Platform Documentation
26.26_Q2 25.52_Q4 25.26_Q2 25.12_Q1 24.50_Q4 24.38_Q3 24.26_Q2 23.50_Q4 23.24_Q2 23.12_Q1 22.50_Q4 22.38_Q3 22.24_Q2
26.26_Q2 25.52_Q4 25.26_Q2 25.12_Q1 24.50_Q4 24.38_Q3 24.26_Q2 23.50_Q4 23.24_Q2 23.12_Q1 22.50_Q4 22.38_Q3 22.24_Q2

Get the playout parameters

Overview

There are two ways for a client application to get the required playout parameters. The one you use depends on the security features that are deployed:

  • Simple method using only content authorisation
    The application discovers the playable content typically through MDS or any of the Content Discovery APIs.

    By making a request to IAS

    , the app retrieves:

    • The content authorisation token

    In this case, the application uses the playout URL that it gets in the metadata response (from MDS or Content Discovery APIs), along with the content authorisation required to obtain a DRM licence.

  • Deployments using SSP's Advanced Security Protection (ASP) mechanisms

    By making a request to URL Builder

    , the app retrieves:

    • The content authorisation token

    • Any other required tokens (e.g., CDN token, watermarking token, etc.)

    • The playout URL

If you are implementing watermarking or CDN authorisation provided by SSP through URL Builder (for example, the ability to revoke CDN access), you should use URL Builder instead of IAS.

See also

Managing CDN token protection in the Subscriber management integration guide