Authentication configuration

Supported authentication types

Adobe Experience Platform Destination SDK supports several authentication types:

  • Bearer authentication
  • OAuth 2 with authorization code
  • OAUth 2 with password grant
  • OAuth 2 with client credentials grant

You can configure the authentication information for your destination via the customerAuthenticationConfigurations parameters of the /destinations endpoint. Refer to the customer authentication configurations section in the destination configuration article and the sections below for specifics around the configurations for each authentication type.

Bearer authentication

To set up bearer type authentication for your destinations, you just need to configure the customerAuthenticationConfigurations parameter in the /destinations endpoint as shown below:


   "customerAuthenticationConfigurations":[
      {
         "authType":"BEARER"
      }
   ]

OAuth 2 authentication

For information how to set up the various supported OAuth 2 flows, as well as for custom OAuth 2 support, read the Destination SDK documentation on OAuth 2 authentication.

When to use the /credentials API endpoint

IMPORTANT

In most cases, you do not need to use the /credentials API endpoint. Instead, you can configure the authentication information for your destination via the customerAuthenticationConfigurations parameters of the /destinations endpoint.

The /credentials API endpoint is provided to destination developers for the cases when there is a global authentication system between Adobe and your destination and Platform customers do not need to provide any authentication credentials to connect to your destination.

In this case, you must create a credentials object by using the /credentials API endpoint. You must also select PLATFORM_AUTHENTICATION in the destination configuration. Read Credentials API endpoint operations for a complete list of operations that you can perform on the /credentials endpoint.

On this page