Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Unable to upload asset to AEM using aem-upload github tool

uafzal
Level 2
Level 2

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

1 Accepted Solution
davidjgonzalezz
Correct answer by
Employee
Employee

admin/admin doesnt work on Cloud Service environments. 

 

You need to make a local account in your AEM as a Cloud Service author env under Tools > Security > Users  and make sure it's permissioned to write to the specified assets folder. 

 

View solution in original post

7 Replies
davidjgonzalezz
Employee
Employee
Can you provide exactly how you are invoking it?
uafzal
Level 2
Level 2

@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.

davidjgonzalezz
Employee
Employee

This is because you are trying to use the tool to upload to a local quickstart-based AEM (the AEM SDK presumably).

 

This tool must be run against a true AEM as a Cloud Service environment (that runs in the Adobe Cloud).

 

uafzal
Level 2
Level 2

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?

davidjgonzalezz
Correct answer by
Employee
Employee

admin/admin doesnt work on Cloud Service environments. 

 

You need to make a local account in your AEM as a Cloud Service author env under Tools > Security > Users  and make sure it's permissioned to write to the specified assets folder. 

 

View solution in original post

uafzal
Level 2
Level 2

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.