Adobe Primetime Authentication (Mobile)
Overview
Adobe Primetime is the gold standard authentication service for the TV Everywhere industry to accomplish the connection between the MVPD (multichannel video programming distributor) and the programmers (content owners) to verify a user’s entitlements.
Supported Platforms
Platform |
Plugin Version |
iOS QB |
0.1.2 |
Android QB |
1.0.2 |
Features
- Authentication.
- This workflow logs in a user with their MVPD.
- Authorization.
- Validates if a user has the entitlements to watch an specific content.
- RSS Format.
- Allows to send content metadata to Adobe’s backend.
- Customization.
- The customer is allowed to change specific parameters of the UI.
Prerequisites
The following parameters are provided through Adobe’s console(Adobe’s documentation) and are necessary to establish correct communication:
- Base URL: Determines which Adobe’s backend environment the plugin should use.
- Requestor ID: The ID assigned for the client by Adobe.
- Resource ID: The ID assigned for the client’s resource by Adobe.
- Software Statement: JWT token issued by Adobe for the specific client’s application.
- URL Scheme (iOS Only): URL Scheme issued by Adobe for the specific client’s application.
- Deep Link (Android Only): Redirect uri assigned by adobe for the specific client's application. This value could be left empty if the client has not configured a custom Redirect Uri in Adobe's console.
Adding the plugin to your application
1.- In the plugin configuration under the section Login you should see the plugin as follows:
2.- Click on the add button to confirm the addition.
Configuring the plugin
1.- After adding the plugin to your app you should see the section “Adobe Authentication Settings” on the right side of the plugin details page.
2.- Depending on the platform chosen for your application version, the proper configuration fields are displayed (Refer to the example image above).
Enter the values described in the Prerequisites section.
3- Only applicable for iOS. Before building your application with adobe’s plugin, please go to the General section of your app version and add the URL Scheme previously described in the Prerequisites section.
*Note: The URL scheme
Important Notes
- The Base URL should never be entered using the protocol of the URL. By default all calls to the endpoint use the HTTPS protocol.
- A Software statement can be issued to cover several platforms or one in particular, please be sure to enter the one assigned to the platform in use.
- There is the option to configure an “Authorization Default Error” which can be used as fallback when Adobe’s backend doesn’t provide an authorization error for a specific MVPD.
Adobe’s Screen and Personalization.
1.- Go to App Studio and select the layout assigned to your app version. Once in App Studio, add the adobe’s plugin screen to your layout.
2.- Select the screen added to activate the screen configuration section. Here you can personalize the UI for the MVDP List. Colors and texts can be modified using the plugin configuration under the section screen design and text
3.- Please use the following schematic as reference:
# |
Component |
Personalization |
1 |
Title |
|
2 |
Instructions |
|
3 |
Header |
|
4 |
MVPD Item |
|
5 |
List separator |
|
6 |
List |
|
Staging Environment
Adobe Primetime Authentication allows customers to have different environments to manage and test MVPD’s integrations before deploying into production. Each environment has its own parameters to establish correct communication.
To configure the plugin to switch between adobe’s environments, the following parameters need to be changed accordingly:
- Base URL.
- Commonly the customer will switch to the staging environment. You can use the following URL’s:
- Android: sp.auth-staging.adobe.com
- iOS: sp.auth-staging.adobe.com/adobe-services
* always review the latest documentation from Adobe link.
- Software Statement.
- URL Scheme (iOS Only).
- Deep Link (Android Only).
* iOS versions will always need to be rebuilt due to the URL Scheme.
User Account Component
Adobe’s plugin is compatible with the user account component. This allows the user to login and logout using a settings section or the side menu of the application. To know more about the UAC please go to this link.
Comments
0 comments
Please sign in to leave a comment.