Fixing HTTP 403 errors when creating technical accounts in AEMaaCS
Creating a technical account in Adobe Experience Manager as a Cloud Service (AEMaaCS) is crucial for operations like content migration. However, HTTP 403 errors occur due to insufficient permissions or misconfiguration. To fix this, verify system admin role assignment, check product profile membership, and validate URL paramteters.
Description description
Environment
Adobe Experience Manager (AEM) as a Cloud Service (AEMaaCS)
Issue/Symptoms
When creating a technical account in AEMaaCS, an HTTP 403 error occur. The error message states: An error occurred attempting to load the provided log. Please check the URL and ensure it is reachable. This issue persists even after manually adding permissions. Misconfigured URL parameters such as technicalUserName, privateKeyName, and certificateName can also contribute to the error.
Resolution resolution
To resolve the HTTP 403 error when creating a technical account in Adobe Experience Manager as a Cloud Service, follow these steps:
- Ensure the System Administrator role is assigned in the Adobe IMS (Adobe Identity Management System) organization via the Adobe Admin Console. Without this role, requests for creating technical accounts will be rejected.
- Confirm addition to the appropriate product profile in AEM. For example, in production environments, ensure membership in the AEM Author Admin product profile corresponding to the targeted environment. This step grants necessary administrative permissions at the AEM level.
- Double-check all URL parameters used during technical account creation, including
technicalUserName,privateKeyName, andcertificateName. Ensure these values are correctly specified and match the expectations outlined in the Create a Technical Account documentation. - Follow the Service credentials authentication documentation to create the technical account again.