Resolve 403 Forbidden error during AEM RDE deployment with IMS technical account
This article describes how to address a 403 Forbidden error encountered when deploying to Adobe Experience Manager (AEM) Rapid Development Environment (RDE) using a technical IMS account through GitHub Actions. The resolution involves verifying and updating Cloud Manager product profile permissions for the technical account.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)
Issue/Symptoms
When you deploy code packages to an AEM RDE environment using GitHub Actions and a technical IMS account, the deployment fails with a 403 Forbidden error. The error typically appears during the deployment command, and the logs display a message similar to the following:
RDECLIInternalError: [ RDECLI:UNEXPECTED_API_ERROR] There was an unexpected API error code 403 with message Forbidden.
Cause
This error occurs when the technical IMS account used for deployment does not have the required Cloud Manager product profile permissions for the specific program and RDE environment. Cloud Manager product profiles and their associated permissions control authorization for RDE deployments.
Resolution resolution
Follow these steps to resolve the issue:
- In the Adobe Admin Console, go to the Cloud Manager product profiles.
- Verify that the technical IMS account used for deployment is assigned to a Cloud Manager product profile.
- Confirm that the assigned product profile grants access to the correct program and includes the required permissions for the target RDE environment.
- If the required product profile does not include the technical account, add the account directly. If the issue persists, do not rely solely on group membership.
- After you update the permissions, retry the deployment through GitHub Actions.
- If the error persists, review the product profile assignments and permissions to ensure that they match the intended program and environment.
- If the issue continues after you verify all permissions, contact Adobe Support for further assistance.