Highlighted

Campaign cloudservice config containing password

steven_rymenan1

24-01-2018

Hi,

We are currently integrating campaign and AEM (AEM 6.3.1.2), we have created email templates and components and are setting up the connection between the 2 tools.

In order to add personalised fields in the email templates in AEM, we have to setup a campaign cloudservice. Doing this manually works and the connection is successful.

However, since we have everything in code, I would like add the content.xml in the code and deploy the configuration. At the moment it is possible to deploy the configuration with the content.xml shown below, but the xml contains a password field, which doesn't get added correctly.

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"
   jcr:primaryType="cq:Page">

   <jcr:content
   cq:cloudservicename="campaign"
   cq:template="/libs/mcm/campaign/templates/configpage"
   jcr:primaryType="cq:PageContent"
   jcr:title="dev"
   sling:resourceType="mcm/campaign/components/configpage"
   apiendpoint="http://191.2.1.100:8080/"
   password="\{cc04499f59300c1cc2035f04befd69fc9d369dec91b23bfdd3e0c8abd600ea70}"
   providerName="campaign"
   saveTokens="sessionToken,securityToken"
   username="aemserver"/>

</jcr:root>

After doing this manually using the AEM UI, I see the password field contains the value above, but this seems to reference another node or datalocation, since it does not work when deploying to a different AEM environment.

Is it possible to pass the password in this xml?

Regards

Steven

Replies

Highlighted

steven_rymenan1

24-01-2018

Since all the environments are automatically provisioned and our deploy process is also automated we want to include it as part of the code and not depend on a manual action.

Highlighted
Highlighted

steven_rymenan1

31-01-2018

When I export the /etc/cloudservices/campaign folder into a package, I see it contains the following:

<?xml version="1.0" encoding="UTF-8"?>

<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"

    jcr:primaryType="cq:Page">

    <jcr:content

        cq:cloudservicename="campaign"

        cq:lastModified="{Date}2018-01-24T10:32:32.357Z"

        cq:lastModifiedBy="admin"

        cq:template="/libs/mcm/campaign/templates/configpage"

        jcr:lastModified="{Date}2018-01-24T10:32:32.353Z"

        jcr:lastModifiedBy="admin"

        jcr:primaryType="cq:PageContent"

        jcr:title="dev"

        sling:resourceType="mcm/campaign/components/configpage"

        apiendpoint="http://192.0.1.1:8080/"

        password="\{ca3b84b5105b472537585a700bfb335d0651a4b181afcd89852e7fa5fd9c7d23}"

        providerName="campaign"

        saveTokens="sessionToken,securityToken"

        username="aemserver"/>

</jcr:root>

However the password is not an encrypted version of the password, because deploying this to a new environment results in a configuration without a password.

Highlighted

marcSis

14-06-2018

We have the same requirement for the Adobe Target integration with cloud services. We want to deploy the config including the encrypted password.

Did you find a solution for this or is the only way to have the deployment scripts setting the password after package installation?