As an AEM developer working in the AEMaaCS environment, it’s common to need to run AEMaaCS local author and publish while developing in your local environment. Typically, authenticating into the AEMaaCS local author environment is straightforward, but accessing the AEMaaCS local publish environment requires some additional steps.
The AEMaaCS local publish environment runs on port 4503, and the security settings are configured by default to align with AEMaaCS setup. If you need to debug the AEMaaCS local publish environment, it’s important to authenticate into the environment, especially for accessing crx/de and system/console.
In this article, we will guide you through the process of authenticating into the AEMaaCS local publish environment.
To access the crx/de and system/console for your AEM publish environment, follow these simple steps:
- Open your web browser and go to http://localhost:4503/libs/granite/core/content/login.html.
- Enter the username “admin” and the password “admin”.
- Once you have successfully logged in, you can navigate to the crx/de and system/console environment.
- Visit crx/de: http://localhost:4503/crx/de/index.jsp
- Visit system/console: http://localhost:4503/system/console/bundles
These instructions are good but they are for AEM 6.5 and earlier, not AEMaaCS (AEM as a Cloud Service). By definition, AEMaaCS runs in the cloud and so you can’t access the instances the ways described here.
This is for local development environment, for the publish AEM instance for AEMaaCS setup. I have re-tested this and it works. Please contact me on linkedin for support.