Fix 403 and 404 errors when accessing admin and content resources

This article explains how to resolve 403 and 404 authorization errors that occur when you try to access admin and content URLs in Adobe Experience Manager as a Cloud Service (AEMaaCS).

Description description

Environment

  • Adobe Experience Manager as a Cloud Service (all versions)
  • Adobe Experience Manager

Issue/Symptoms

The user is unable to access certain administrative and content URLs in AEM as a Cloud Service, encountering the following errors:

  • When accessing the Sites Admin URL: https://tools.aem.live/tools/site-admin/index.html?org=
    The following error is displayed: 403 Forbidden
  • When accessing a content editing URL: https://da.live/edit#/org-id/site-name/index
    The following error is displayed: Unable to fetch ‘/index.md’ from ‘html2md’: (404) - not authorized to access resource: https://content.da.live/org-id/site-name/
  • The user requests admin access to resolve these errors.

Cause

The system returns these errors when the user does not have the required admin permissions to access the requested resources in AEM as a Cloud Service.

Resolution resolution

To resolve this issue, follow these steps:

  1. Verify Admin Group Membership

    • Confirm that the user experiencing the issue is a member of the appropriate admin group (for example, Config Admin) for the tenant in AEM as a Cloud Service.
    • Only users with admin privileges can access the Sites Admin and certain content resources.
  2. Identify an Existing Administrator

    • Contact the individual who performed the initial setup of the AEM as a Cloud Service project for the tenant. This user is typically assigned as an administrator and can grant additional admin access.
  3. Review Current Admin Users

    • An existing administrator should visit the User Admin tool to view the list of current admin users.
  4. Add the User as an Administrator

    • Follow the steps in the [official documentation](https://www.aem.live/developer/ue-tutorial#connect-aem-code-sync-bot: :text=Click%20Fetch%20Users%20and%20confirm%20that%20there%20were%20no%20users%20created.) to add the user to the admin group.
    • After being added, the user should log out and log back in to ensure the new permissions take effect.
  5. Test Access

    • The user should try to access the previously restricted URLs again to confirm that the 403 and 404 errors are resolved.
recommendation-more-help
experience-cloud-kcs-help-kbarticles