search

AdobeDocs / experience-manager-cloud-service.en

This is the repository for Adobe Experience Manager as a Cloud Service documentation. Your contributions to the documentation are welcome.
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service
MIT License
3 stars 41 forks source link

Content Set Execution API #147

Open pat-lego opened 1 year ago

pat-lego commented 1 year ago

The execute content set API requires users to manually add the user to AEM Product profile for source and destination as well as the Deployment Manager product profile.

Users are expected to copy the technical account email address and provide that to the necessary product profiles or else the execution of the API will not work.

bohnertchris commented 1 year ago

Thanks for the issue, @pat-lego. Can you please provide some more detail on use case and where this should be incorporated into the docs?

pat-lego commented 1 year ago

Specifically at this location https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developer-tools/content-copy.html?lang=en#permissions it mentions what permissions you need but it does not mention how to set them up for yourself.

In the case that you use Adobe Developer Console you need to copy the technical account email and add it as an enterprise ID in the Admin Console under all the appropriate roles.

If you do not do this you get a 403 error until this manual step is done.

bohnertchris commented 11 months ago

Thanks for the direct link, @pat-lego. We do already provide a link to the documentation for setting up permissions using the Admin Console. It is linked directly below the list of permissions needed. Is this not sufficient or is there something missing from that?

pat-lego commented 11 months ago

Having the link is good but its missing what user to put in the administrator's profile. Most people would assume its them that need to go into the administrator which is true UNLESS you are using the API.

In that case it's the TECHNICAL ACCOUNT EMAIL you need to add but it's not documented that this is the case and for that reason all API calls to will fail with a 403.

This document you are referring to [1] is more of a generic how to add a user to a product profile, which is a good document. What needs to be added to this doc [2] is what user to add to [1] when using API calls to content backflow.

[1] https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/onboarding/concepts/aem-cs-team-product-profiles.html?lang=en

[2] https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/developer-tools/content-copy.html?lang=en#permissions