Hi, @davidjgonzalezzzz yes, I have the same scope as you mentioned. I compared the files for Asset Share Commons in my Local AEM SDK and Cloud. Looks like, the following are missing in cloud: /etc/cloudsettings/asset-share-commons/etc/notification/email/asset-share-commons/etc/notification/email/rep...

I am using Assets HTTP API - I am trying to find a way to send data in body or payload. I know some of the endpoints accept data in the request body. For example, when creating a folder, we use the following: (See how the folder name is sent as form-data and not in the URL)POST /api/assets/* -F"name...

I am trying to integrate Asset Share Commons into an existing AEM maven project. The build and deployment to a local AEM SDK as well as in the Cloud are successful - the features work fine in AEM local SDK. In the cloud, I am able to open the Asset Share Commons Site but, the "download", "add to car...

Thank you. It worked. I made sure the user has the correct write permissions (for example: rep:write on /content/dam) or my user needs to be a part of DAM Users Group.

I have tried that against an author AEM as a Cloud Service Environment but getting "ENOTAUTHORIZED" error.I am an admin - any idea what else I am missing?

@davidjgonzalezzI am using the script given in the example: https://github.com/adobe/aem-upload#uploading-files My target URL is 'http://localhost:4502/content/dam/'; Also, I am using the .withBasicAuth('admin:admin') option to authenticate.

-

I am using the aem-upload tool to upload an asset to an AEM instance. The documentation says "all AEM as a Cloud Service instances will have direct binary upload enabled, so this library will work with those."But, I get the following error.  Error: direct binary access not supported