Adobe Marketing Cloud Connector

Important

Connectors continue to be released outside the IDM release. For the latest documentation, refer to the ICF documentation.

The Adobe Marketing Cloud connector enables you to manage profiles in an Adobe Campaign data store. The connector supports a subset of the OpenICF operations, as listed in "OpenICF Interfaces Implemented by the Adobe Marketing Cloud Connector".

To use this connector, you need an Adobe ID.

Before You Start

The Adobe Marketing Cloud connector requires the JSON Web Token library. Before you start, download this library and copy it to the /path/to/openidm/lib directory.

You must also configure a new integration on AdobeIO, as shown in the following steps. Note that these steps assume a specific version of the AdobeIO user interface. For information on the current version, see the corresponding Adobe documentation.

The integration requires a public certificate and private key that will be used to sign the JWT token.
You can use IDM's generated self-signed certificate and private key to test the connector. In a production environment, use a CA-signed certificate and key.
Export IDM's self-signed certificate as follows:
1. Export the certificate and key from JCEKS to standardized format PKCS #12:
```
keytool \
-importkeystore \
-srckeystore /path/to/openidm/security/keystore.jceks \
-srcstoretype jceks \
-destkeystore /path/to/keystore.p12 \
-deststoretype PKCS12 \
-srcalias openidm-localhost \
-deststorepass changeit \
-destkeypass changeit
```
2. Export the certificate:
```
openssl pkcs12 \
-in /path/to/keystore.p12 \
-nokeys \
-out /path/to/cert.pem
```
3. Export the unencrypted private key:
```
openssl pkcs12 \
-in /path/to/keystore.p12 \
-nodes \
-nocerts \
-out /path/to/key.pem
```
Log in to https://console.adobe.io/ and select Integrations > New Integration.
Select Access an API > Continue.
Under the Experience Cloud item, select Adobe Campaign > Continue, then select New integration > Continue.
Enter a name for the new integration, for example, IDM-managed, and a short description.
Drag the public certificate that you exported previously into the Public keys certificates box.
Select a license, then select Create Integration.
Select Continue to integration details to obtain the Client Credentials required by the connector.
You will need these details for the connector configuration.

Configuring the Adobe Marketing Cloud Connector

Create a connector configuration file for the Adobe Marketing Cloud connector and place it in your project's conf/ directory.

IDM bundles a sample configuration file (/path/to/openidm/samples/example-configurations/provisioners/provisioner.openicf-adobe.json) that you can use as a starting point. Alternatively, you can create the configuration by using the Admin UI. Select Configure > Connectors > New Connector and select Adobe Marketing Cloud Connector - 1.5.20.11 as the connector type.

The following example shows an excerpt of the provisioner configuration. Enable the connector (set "enabled" : true) then edit at least the configurationProperties to match your Adobe IO setup:

"configurationProperties" : {
    "endpoint" : "mc.adobe.io",
    "imsHost" : "ims-na1.adobelogin.com",
    "tenant" : "https://example.adobesandbox.com/",
    "apiKey" : "",
    "techAccId" : "example@techacct.adobe.com",
    "orgId" : "example@AdobeOrg",
    "clientSecret" : "CLIENT_SECRET",
    "privateKey" : "PRIVATE_KEY"
},
...

endpoint: The Adobe IO endpoint for Marketing Cloud. mc.adobe.io by default - you should not have to change this value.
imsHost: The Adobe Identity Management System (IMS) host. ims-na1.adobelogin.com by default - you should not have to change this value.
tenant: Your tenant (organization) name or sandbox host.
apiKey: The API key (client ID) assigned to your API client account.
techAccId: Your Technical account ID, required to generate the JWT.
orgId: Your organization's unique ID, for example 12345@AdobeOrg.
clientSecret: The client secret assigned to your API client account.
privateKey: The private key used to sign the JWT token, corresponds to the public key certificate that you attached to the integration.

For a list of all the configurable properties, see "Adobe Marketing Cloud Connector Configuration".

When your connector is configured correctly, you can test its status by running the following command:

curl \
--header "X-OpenIDM-Username: openidm-admin" \
--header "X-OpenIDM-Password: openidm-admin" \
--header "Accept-API-Version: resource=1.0" \
--request POST \
"http://localhost:8080/openidm/system?_action=test"
[
  {
    "name": "adobe",
    "enabled": true,
    "config": "config/provisioner.openicf/adobe",
    "connectorRef": {
      "bundleName": "org.forgerock.openicf.connectors.adobecm-connector",
      "connectorName": "org.forgerock.openicf.acm.ACMConnector",
      "bundleVersion": "1.5.20.11"
    },
    "displayName": "Adobe Marketing Cloud Connector",
    "objectTypes": [
      "__ALL__",
      "account"
    ],
    "ok": true
  }
]

A status of "ok": true indicates that the connector can reach the configured Adobe integration.

OpenICF Interfaces Implemented by the Adobe Marketing Cloud Connector

The Adobe Marketing Cloud Connector implements the following OpenICF interfaces.

Create

Creates an object and its uid.

Delete

Deletes an object, referenced by its uid.

Schema

Describes the object types, operations, and options that the connector supports.

Script on Connector

Enables an application to run a script in the context of the connector. Any script that runs on the connector has the following characteristics:

The script runs in the same execution environment as the connector and has access to all the classes to which the connector has access.
The script has access to a connector variable that is equivalent to an initialized instance of the connector. At a minimum, the script can access the connector configuration.
The script has access to any script-arguments passed in by the application.

Search

Searches the target resource for all objects that match the specified object class and filter.

Test

Tests the connector configuration. Testing a configuration checks all elements of the environment that are referred to by the configuration are available. For example, the connector might make a physical connection to a host that is specified in the configuration to verify that it exists and that the credentials that are specified in the configuration are valid.

This operation might need to connect to a resource, and, as such, might take some time. Do not invoke this operation too often, such as before every provisioning operation. The test operation is not intended to check that the connector is alive (that is, that its physical connection to the resource has not timed out).

You can invoke the test operation before a connector configuration has been validated.

Update

Updates (modifies or replaces) objects on a target resource.

Adobe Marketing Cloud Connector Configuration

The Adobe Marketing Cloud Connector has the following configurable properties.

Basic configuration properties

Property	Type	Default
`endpoint`	`String`	`mc.adobe.io`
The Adobe IO endpoint for Marketing Cloud. mc.adobe.io by default - you should not have to change this.

`imsHost`	`String`	`ims-na1.adobelogin.com`
Adobe Identity Management System (IMS) host. ims-na1.adobelogin.com by default - you should not have to change this.

`tenant`	`String`	`null`
Your tenant (organization) name or sandbox host.

^[a] Indicates whether the property value is considered confidential, and therefore encrypted in OpenIDM. ^[b] A list of operations in this column indicates that the property is required for those operations.

Adobe Integration Properties

Property	Type	Default
`apiKey`	`GuardedString`	`null`
The API key (client ID) assigned to your API client account

`technicalAccountID`	`String`	`null`
Your Technical account ID, required to generate the JWT

`organizationID`	`String`	`null`
Your organizations unique ID, for example 12345@AdobeOrg

`clientSecret`	`GuardedString`	`null`
The client secret assigned to your API client account

`privateKey`	`GuardedString`	`null`
The private key used to sign the JWT token, corresponds to the public key certificate attached to the integration

`accessToken`	`GuardedString`	`null`
The OAuth Access Token for the application

^[a] Indicates whether the property value is considered confidential, and therefore encrypted in OpenIDM. ^[b] A list of operations in this column indicates that the property is required for those operations.