Dynamic Client Registration Overview dynamic-client-registration-overview

IMPORTANT
The content on this page is provided for information purposes only. Usage of this API requires a current license from Adobe. No unauthorized use is permitted.

Dynamic client registration represents an authorization mechanism defined by RFC 7591, and it is based on the OAuth 2.0 authorization framework that is described by RFC 6749.

Adobe Pass provides a dynamic client registration service that enables access to the following protected APIs:

IMPORTANT
Dynamic client registration authorization mechanism replaces older Adobe Pass Authentication solutions that are subject to be discontinued:
  • The signed requestor ID mechanism.
  • The domain listing mechanism.
  • The API key mechanism.

With the adoption of dynamic client registration the main benefits are:

  • Enhanced security.
  • Unified model across platforms.
  • Fine-grained control of your application’s lifecycle.

To learn more about how to manage and use dynamic client registration, refer to the following sections.

Dynamic Client Registration Management dynamic-client-registration-management

The dynamic client registration management process allows client applications running on specific platforms and needing access to specific Adobe Pass Authentication APIs to register through the Adobe Pass TVE Dashboard.

The Adobe Pass TVE Dashboard is a tool for Adobe Pass Authentication customers (Programmers) to manage their configuration and data. This self-service dashboard enables a range of functionalities that are described in the Adobe Pass TVE Dashboard User Guide documentation.

In case you have access to the Adobe Pass TVE Dashboard, follow the steps in the sections below to create a registered application and download the software statement.

Manage registered applications manage-registered-applications

IMPORTANT
In case you do not have access to the Adobe Pass TVE Dashboard, create a ticket through our Zendesk and ask your Technical Account Manager (TAM) to create a registered application and share the software statement with you.

There are two available ways you can create a registered application:

  • Programmer level

    The programmer-level registration process allows you to create a registered application linked to all available channels or a selected subset of channels. For more details, refer to the TVE Dashboard User Guide for Programmers documentation.

  • Channel level

    The channel-level registration process allows you to create a registered application linked only to the current selected channel. For more details, refer to the TVE Dashboard User Guide for Channels documentation.

IMPORTANT
It is recommended to create registered applications with more specific and limited permissions to enhance security and prevent unauthorized access. Therefore, when creating registered applications, consider using narrower options for the assigned channels, platforms, and scopes.
It is recommended to create a new registered application for each major update of your client application to manage its life cycle and usage. If necessary, create a ticket through our Zendesk and ask your Technical Account Manager (TAM) to revoke a registered application in order to block the functionality of a specific client application version.

Manage software statements manage-software-statements

IMPORTANT
In case you do not have access to the Adobe Pass TVE Dashboard, create a ticket through our Zendesk and ask your Technical Account Manager (TAM) to create a registered application and share the software statement with you.

Before downloading a software statement, ensure you have a registered application created as described in the Manage registered applications section that meets your client application requirements.

There are two available ways you can download a software statement based on the level where the registered application was created:

The software statement is a JSON Web Token (JWT) that contains information about your client application software as a bundle. When presented to the Retrieve client credentials API, the software statement is digitally signed using JSON Web Signature (JWS).

For more detailed explanation on what software statements are and how they work, refer to the RFC 7591 documentation.

Dynamic Client Registration Flow dynamic-client-registration-flow

In summary, the dynamic client registration authorization mechanism involves several steps:

Management

Flow

Refer to the Dynamic Client Registration Flow documentation to better understand how to access Adobe Pass protected APIs. Furthermore, you can also watch this webinar recording, which provides more context and includes a demo.

recommendation-more-help
3f5e655c-af63-48cc-9769-2b6803cc5f4b