(Legacy) Android Application Registration android-application-registration

NOTE
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.
IMPORTANT
Make sure you stay informed about the latest Adobe Pass Authentication product announcements and decommissioning timelines aggregated in the Product Announcements page.

Introduction intro

Starting with version 3.0 of the Android AccessEnabler SDK, we are changing the Authentication mechanism with Adobe’s servers. Instead of using a public key and secret system to sign the requestorID, we are introducing the concept of a Software Statement string that can be used to obtain an access token that is later used for all calls that the SDK makes to our servers. In addition to a Software Statement you will also need to create a deep link for your application.

For more information, see Dynamic Client Registration Overview.

What is a Software Statement? what

A Software Statement is a JWT token that contains information about your application. Every application should have a unique software statement that is used by our servers to identify the application in Adobe’s system.

The Software Statement needs to be passed when you initialize the AccessEnabler SDK. It is used to register the application with Adobe. Upon registration, the SDK receives a client ID and a client secret, which is used to obtain an access token. Any call that the SDK makes to Adobe servers requires a valid access token. The SDK is responsible for registering the application, obtaining, and refreshing the access token.

NOTE
Software Statements are app-specific and an individual Software Statement cannot be used for more than one application. Please note that Programmer level software statements have the same constraint, they can only be used for single application, whether single channel or multi-channel.

How to obtain a Software Statement how-to-get-ss

Here are ways you can obtain a Software Statement.

If you have access to Adobe’s TVE Dashboard

  1. Open your browser and navigate to Adobe Pass TVE Dashboard.

  2. Navigate to Channels section, then select your channel.

  3. Navigate to the Registered Applications tab.

  4. Click Add new application.

  5. Name the application and specify a version.

  6. Select the platforms on which the application will be available (Android in this case).

  7. Provide a Domain Name by choosing from a list of domains already configured for your Programmer.

  8. Push your changes to the server, then navigate back to you Channel’s Registered Applications tab.

    You should see a list with all registered applications. Select Download on the application that you created. You may need to wait a few minutes before your Software Statement it’s ready for download.

    A text file downloads. Use its contents as your Software Statement.

For more information, see Dynamic Client Registration Management.

If you don’t have access to Adobe’s TVE Dashboard

Submit a ticket to tve-support@adobe.com. Include the necessary information like channel, application name, version and platforms. Someone from our support team will create a software statement for you.

How to use the Software Statement how-to-use-ss

After you obtain your Software Statement, you need to pass it as a parameter in the Access Enabler constructor. We recommend hosting the Software Statement on a remote location. This way, you can easily revoke and change the Software Statement without releasing a new version of your application.

On Android, use as deep link value the reverse of the domain name selected when you created the Software Statement

Created deep link should have a unique value on the Android device. When multiple applications use the same deep link value, the authentication and logout flows will interfere.

In your application’s resource file strings.xml add the following code:

    <string name="software_statement">softwarestatement value</string>
    <string name="redirect_uri">com.domain_name</string>
recommendation-more-help
3f5e655c-af63-48cc-9769-2b6803cc5f4b