AEM exposes a variety of HTTP endpoints that can be interacted with in a headless manner, from GraphQL, AEM Content Services to Assets HTTP API. Often, these headless consumers may need to authenticate to AEM in order to access protected content or actions. To facilitate this, AEM supports token-based authentication of HTTP requests from external applications, services or systems.
In this tutorial well explore how an external application can programmatically authenticate and interact with to AEM as a Cloud Service over HTTP using access tokens.
Ensure the following are in place before following along with this tutorial:
Access to am AEM as a Cloud Service environment (preferably a Development environment or a Sandbox program)
Membership in the AEM as a Cloud Service environment’s Author services AEM Administrator Product Profile
Membership in, or access, to your Adobe IMS Org Administrator (they will have to perform a one-time initialization of the Service Credentials)
The latest WKND Site deployed to your Cloud Service environment
External Application overview
This tutorial uses a simple Node.js application run from the command line to update asset metadata on AEM as a Cloud Service using Assets HTTP API.