Adobe Primetime Authentication | Product description

Last updated: August 12, 2015

What is Adobe Primetime Authentication?

Adobe Primetime Authentication is a hosted service that serves as a proxy between programmers and MVPDs to verify a user’s entitlement to content based on their pay TV or other subscription.

Product or Service

License Metric


Primetime Authentication

Stream or

Successful Play Request

On-demand Servcies

Additional Services and Workflows


On-demand Services

Product limitations

The Additional Services and Workflows are limited to the following functionality:

1.  Platform Services

Platform Services includes maintenance, escalation and updates to existing MVPD integrations, which may include:

  • Full MVPD migration after a technology upgrade/vendor change
  • Updated endpoints to support new functionality like preflight authorization
  • Adding new user metadata parameters
  • Automatic notifications of MVPD outages

2.  Basic Workflows

  • Authentication, authorization, pre-authorization and logout calls
  • SSO per platform (when technically available)
  • Parental Control workflows (passing of max rating parameters from the MVPD via user metadata API calls and passing asset level ratings from the Programmer to the MVPD)
  • User Metadata calls related to User ID information
  • Basic monthly metrics - delivered once a month in spreadsheet format, includes authentication and authorization metrics broken down per day/MVPD, as well as aggregated
  • Supported Platforms: Flash Player, JavaScript, iOS, Android, Windows 8

3.  Premium Workflows

  • Clientless API platform, which allows customers to build workflows for platforms where the Pass SDK is not available – such as Apple TV, Roku, Xbox360, Xbox1.
  • Degradation API – allows Customer to bypass normal authentication and authorization flows if needed. Currently supported rules: MVPD disable, AuthN all, AuthZ all, AuthZ never. enables Programmers to access the Degradation API, but does not include a console for management (console must be built by Customer)
  • Temp Pass MVPD – allows Customer to provide Permitted TVE Content for free for a limited time. Note: Temp Pass has some limitations. Please ask for more details before fully deploying this feature.
  • User metadata flows different from Parental Controls ones including: household ID, is head of household flag, postal code, channel line-up.
  • Simple Demo MVPD with a 10 user accounts – allows a live integration with a generically branded demo MVPD to be used for sales or demo purposes.
  • One Demo MVPD with co-branding, admin rights and up to 100 accounts – an extension of the simple Demo MVPD
  • Integration with company’s LDAP – a one time only integration between Customer’s LDAP system and the Adobe Pass service. Requires SAML or OAuth support on the Customer systems.
  • Token Validation Service

4.  Premium Reporting

  • ESM 2.0 API – provides access to real-time authentication and authorization events + breakdowns per various timeframe periods, MVPD, SDK-type, requestor ID.


Stream means (A) each time a Content User initiates playback to view Ads or Customer Content via a Video Player; or (B) each viewing interval of up to 30 minutes that has elapsed since a new Stream has been counted for the same piece of Customer Content or Ad.  For example, if a Consumer watches a feed for 85 minutes, the Content User has watched 3 Streams.

Successful Play Request means each instance of a Content User requesting to view a unit of Authorized Content and the Service validates the Content User as entitled to view the unit of Authorized Content, regardless of (i) the number of calls made to the TV-E server to validate such request, (ii) the length and number of streams of the unit of Authorized Content, and (iii) whether or not the unit of Authorized Content is ultimately delivered to the Content User. For the avoidance of doubt, if the Service determines that a Content User is entitled to view a unit of Authorized Content but the Authorized Content does not start due to a geo restriction or other rule outside of the control of the Service, a Successful Play Request will still be counted.  Customer shall make an API call to the Service with every individual play request.


Get help faster and easier

New user?