Hello,
I've been trying to use the HTTP Assets API to upload files, create folders, and publish assets in our AEM Production environment through Postman. While I'm able to successfully accomplish these tasks in our lower environments (local, dev, stage) I'm always blocked doing so in Production.
For example, when trying to create a new folder in production using this endpoint: "https://prod-example-url/api/assets/northerntrust/test/newTest"
With this in the body: { "class":"assetFolder", "properties":{ "title":"Test Folder9" } }
I get a 500 error: Unable to create node at /content/dam/northerntrust/test/newTest
Similarly, I've gotten errors when trying to replicate content that state: Warn: No rights to replicate. Request for de/activation got issued for/content/dam/northerntrust/test/test.doc
I have verified that the authorization is provided and that the user making the request has the proper permissions. I have also attempted to include a CSRF token. Other posts have suggested checking the CSRF filters in "/system/console/configMgr". I did this on local where I have access and POST request is added in the filters and the POST requests there are still successful so I do not believe this is the problem.
Does anyone have any idea what configuration settings (or other issues) in production could be resulting in the failed POST requests?
Greatly appreciate any insight!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi,
Please ensure that the dispatcher is not blocking your call. Additionally, double-check the logs for more information. If no additional details are present, enable logging to capture more information about the issue. Meanwhile, please review my response on this thread:
Hi,
Please ensure that the dispatcher is not blocking your call. Additionally, double-check the logs for more information. If no additional details are present, enable logging to capture more information about the issue. Meanwhile, please review my response on this thread:
Thank you. We ended up downloading the Prod logs and they showed it was a permissions issue that we thought we had, but didn't previously account for.
Views
Replies
Total Likes
What was the issue? I'm dealing with the same thing. Thanks!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies