AEM & Adobe Target Integration

[test1234567]

Hello Community,

We are in the process of setting up the integration between AEM and Adobe Target. Could you please let me know which PIDs I need to use to create OSGi configs so that they are deployed as part of the code? Additionally, there are some existing configs that were created manually. I want to ensure that these existing configurations are not overwritten and that the new config is added as part of the deployment.

Security -> Adobe IMS Configurations

Adobe IMS Technical Account Configuration

Cloud Services -> Legacy Cloud Services -> Adobe Target Configurations

[Umesh_Thakur]

for IMS configuration you can use com.adobe.granite.auth.oauth.accesstoken.provider as PID to configure this thru your code I would suggest first configure IMS in your local then from /apps/system copy or move it to your code
cloud configuration for target can be found at /etc/cloudservices/testandtarget path.
same here first configure then move it to code.
for existing configuration you can follow the same but keep filter.xml change with proper mode in mind.
hope this helps

Umesh Thakur

[test1234567]

Thanks for your reply. For the PID com.adobe.granite.auth.oauth.accesstoken.provider, do I also need to add a suffix to the PID, as shown below, to avoid overriding the existing configuration?

com.adobe.granite.auth.oauth.accesstoken.provider-project.cfg.json

[Umesh_Thakur]

Yes you can add suffix, in-fact if you add the configuration thru IMS console, you can find a hash string as suffix with the PID so that is alway a good practice to have one with suffix if you are expecting more than one configuration .

Hope this helps

Umesh Thakur

[test1234567]

I tried updating the configuration by creating a new one, but the factory PID is missing. I'm not sure if it is being considered as a valid configuration.

Also, after deployment, the configuration is missing under Security → Adobe IMS Configurations.

According to Adobe’s documentation, we are required to use a specific naming convention for the configuration file. If I use a hyphen (-) before the <randomnumber>, the configuration does not get installed. It only installs if I use a dot (.) in the name before <randomnumber>, like this:com.adobe.granite.auth.oauth.accesstoken.provider-<randomnumber>.config.
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/using/config-oauth#o...

[Umesh_Thakur]

It seems your config is not getting resolved as there are some issue with the config

here is the example from my local.

/apps/system/config/com.adobe.granite.auth.oauth.accesstoken.provider.c3450e9d-3bc1-46ed-849f-25d1ce8ce945.cfg.json

if you follow the same pattern, it will work for sure.

look for in AEM configuration:

Adobe Granite Access Token provider using Client Credentials/JWT Credential flow

as it is there in below image:

Hope this helps

Umesh Thakur

[test1234567]

Thank you for your reply. I was able to successfully deploy the configuration. The only issue I encountered was that the 'Secret Key' was missing, so I had to add it manually. I'm not sure which key name I should use to specify the Secret Key as part of the configuration. Could you please advise?

E.g. 
for client.id:

auth.token.provider.client.id

for org id:

auth.token.provider.orgId