How to login to AEMaaCS Local Publish crx/de system/console

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:

  1. Open your web browser and go to http://localhost:4503/libs/granite/core/content/login.html.
  2. Enter the username “admin” and the password “admin”.
  3. Once you have successfully logged in, you can navigate to the crx/de and system/console environment.
  4. Visit crx/de: http://localhost:4503/crx/de/index.jsp
  5. Visit system/console: http://localhost:4503/system/console/bundles

Hello, I am an enthusiastic Adobe Community Advisor and a seasoned Lead AEM Developer. I am currently serving as an AEM Technical Lead at MNPDigital.ca, bringing over a decade of extensive web engineering experience and more than eight years of practical AEM experience to the table. My goal is to give back to the AEM Full Stack Development community by sharing my wealth of knowledge with others. You can connect with me on LinkedIn.

2 thoughts on “How to login to AEMaaCS Local Publish crx/de system/console

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

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

Leave a Reply

Your email address will not be published. Required fields are marked *


Back To Top