I am working on migrating assets from AEM 6.5 env to AEM cloud. When I try to make a curl to production instance I get 401.
The process which I follow is :
1. use technical account to generate JWT token.
2. Use the JWT token and add it to Curl as Bearer token and upload the data using /asset api microservice.
When I follow the above process in lower env (Dev env), I am able to upload assets successfully but same process is not working on Production and I am getting 401.
I have also added the my technical account's user in administrator group and also able to generate the JWT token successfully.
Is there anything that I have missed which could be causing this issue?
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @AshishSh5,
According to Adobe’s documentation, here are the guidelines to be followed when implementing server-to-server API integration:
From your description, I believe you might have missed out exchanging the JWT token for an access token using Adobe's IMS API.
Below are some documentation links with further details:
Hope this helps,
Vinay
Views
Replies
Total Likes
Views
Replies
Total Likes
Please verify if the user is synced to the AEM Production Environment or not.
If, for any reason, the technical account user is not yet present in AEM, you can create the account by sending an HTTP request with a valid token to AEM. This can be accomplished through tools like the curl command or Postman. You might not be able to access any resource, as group association is pending. But, a user corresponding to service account will be created.
Once user is created, check its group association in AEM
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies