Adobe Campaign Trigger Installation

[Luca_Lattarini]

Hello guys,

Im installing the pipeline for Adobe Campaign Classic. Where can I find appName?

<pipelined autoStart="true" appName="adobecampaign_triggers" authPrivateKey="@qQf146pexBksGvo0esVIDO(…)"/>

Thanks

[Darren_Bowers · Accepted solution]

Hi @Luca_Lattarini - the appName property was the Application ID value used with the old legacy oAuth analytics connectors.

If you are looking for the value you can find it in the Legacy OAuth Applications tab in Analytics

As this authentication mechanism is being retired you need to port the auth mechanism over to Adobe.io: https://experienceleague.adobe.com/docs/campaign-classic/using/integrating-with-adobe-experience-clo...

Cheers

Darren

[Luca_Lattarini]

Hello @Darren_Bowers 

I followed the mentioned link by adding to conf-<instance.xml> these lines

1) 

<pipelined autoStart="true" authType="<private key from adobe console io encoded base64>"/>

2) added the code below by executing nlserver ..... under AC container

<ims authIMSTAClientId="" authIMSTAClientSecret=""
authIMSTAId="" authIMSTAPrivateKey=""/>

Now I am getting this error

Any suggestion? 

Yet, to encode private key I used this website https://www.base64encode.org/.Is correct?

Thanks

[Darren_Bowers]

Hi @Luca_Lattarini - are you trying to use the legacy Analytics oAuth or the new Adobe.io JWT auth method here?

[Luca_Lattarini]

Hello @Darren_Bowers, this is the new Adobe.io JWT.

[Darren_Bowers]

Hi @Luca_Lattarini. For the new adobe.io setup the only things you need in the pipelined tag is authType e.g. <pipelined ... authType="imsJwtToken" ... /> . I left in the appName from the old app and set autoStart="true" as well. The <ims> node should be configured using the nlserver command that they give you in Step 2.4. This includes the base64 encoded private key that you generated during the project setup.

Cheers Darren

[Luca_Lattarini]

Hello Darren, where can I find this authType=""? Is the mentioned in the pic?

do you have an example of pipeline tag by using the new approach? is it correct  <pipelined autoStart="true"  authType="">by considering we dont have the application id for the new approach?

[Darren_Bowers]

Hi @Luca_Lattarini - Have a look at the very last step (Step 3) in the instructions: https://experienceleague.adobe.com/docs/campaign-classic/using/integrating-with-adobe-experience-clo... - the only thing you need is the autoStart and authType parameters. appName and authPrivateKey are ignored once you set authType="imsJwtToken"

FYI you don't replace imsJwtToken with anything - that is the property value

<pipelined autoStart="true" authType="imsJwtToken" appName="notUsed" authPrivateKey"" />

Cheers Darren

[Luca_Lattarini]

Hello @Darren_Bowers, fist of all let me tell you thank you so much for your time.

I followed your answer by adding this <pipelined autoStart="true" appName="notUsed" authPrivateKey="" authType="imsJwtToken" /> to  the config-instance.xml

FYI : I left authPrivateKey=""  empty and this tag was generated successfully 

<ims authIMSTAClientId="xxxxx" authIMSTAClientSecret="xxx"
authIMSTAId="xxxxxxx@techacct.adobe.com" authIMSTAPrivateKey="@z57TDDsVc5qFDH+8vMMVxnkCDm0dc4Hixkq6oUNOV42yyfadYEqLmg/"  the encoded key/>

But i m still getting this issue

Maybe I encoded wrongly the private key? 

[Darren_Bowers]

Hi @Luca_Lattarini - No problems. I worked for many weeks with Adobe Support to figure this out so I feel your pain! The documentation is very sparse...

Have you created an Analytics Product Profile and linked in the Adobe.io API service into the access?

[Luca_Lattarini]

Hello @Darren_Bowers,