Repository Browser visibility issues in AEM Developer Console for publish instances
This article explains how to fix the issue where the Repository Browser is missing in the developer console for publish instances in Adobe Experience Manager (AEM) as a Cloud Service – Sites. The issue typically occurs due to incorrect product profile assignments or missing permissions. To resolve the issue, update product profiles and permissions.
Description description
Environment
Product: Adobe Experience Manager as a Cloud Service (AEMaaCS) – Sites
Instance Type: Publish
Key Features: Developer Console, Repository Browser
Issue / Symptoms
You can’t access the Repository Browser in the Developer Console for publish instances. Common symptoms include:
- The Repository Browser tab is missing under All publishers.
- A 403 Forbidden error appears when accessing paths like /content.
- Nodes that were previously visible no longer appear due to permission issues.
Resolution resolution
To resolve this issue, follow these steps:
- Assign valid product profiles in the Admin Console, such as AEM Administrators - publish - Program… or AEM Users - publish - Program…", and avoid deprecated profiles, including AEM Users
<random chars>or outdated group-based assignments. - Confirm that you have the necessary permissions to access the Repository Browser, and ensure you have at least read access to publish instances through your assigned product profiles.
- Log in to the Developer Console before accessing the Repository Browser URL directly, and use an incognito browser session to avoid issues caused by caching or existing sessions.
- Review recent changes in user group and product profile synchronization within AEM, and ensure administrative credentials and product profiles are properly synced for affected instances.
- Capture detailed HAR logs if the issue persists, starting from login through publisher pod selection, and refer to Adobe’s documentation for guidance on generating HAR files.
- After making updates, log out of the Developer Console and log back in. Then, check if the Repository Browser is accessible under All publishers.
3d58f420-19b5-47a0-a122-5c9dab55ec7f