DocumentationExperience Cloud KCS

RDE CLI commands fail in CI/CD when the technical account is not authorized

Last update: July 20, 2026

In AEMaaCS, Adobe I/O CLI commands for an RDE can fail in CI/CD with 403 errors when the technical account lacks required access or the OAuth configuration is incorrect. To fix this, verify the required product profile, confirm RDE authorization, and review the CLI configuration.

Description description

Environment:

  • Adobe Experience Manager as a Cloud Service (AEMaaCS)
  • Rapid Development Environment (RDE)
  • Adobe I/O CLI
  • CI/CD pipelines using service credentials

Issue/Symptoms:

  • RDE CLI commands fail in CI/CD even though authentication appears to complete successfully.
  • aio cloudmanager:list-programs returns [ CloudManagerSDK:ERROR_LIST_PROGRAMS] Cannot retrieve programs: https://cloudmanager.adobe.io/api/programs (403 Forbidden).
  • aio aem:rde:status or aio aem:rde:install returns [ RDECLI:UNEXPECTED_API_ERROR] code 403 with message Forbidden.
  • aio aem:rde:status or aio aem:rde:install returns [ RDECLI:NETWORK_ERROR] Could not communicate with the server … Code: NETWORK_ERROR.

Cause:

The Adobe I/O CLI checks Cloud Manager permissions at runtime. If the technical account is not directly assigned to the required Cloud Manager product profile or is not authorized for the RDE, the Cloud Manager API can return HTTP 403 and the RDE commands can fail. An incorrect OAuth configuration can cause the same behavior.

Resolution resolution

To fix this issue, follow these steps:

  1. In Admin Console, verify that the technical account is directly assigned to the Cloud Manager Developer - Cloud Service product profile.
  2. If the pipeline uses service credentials, add the technical account to the RDE authorized users list.
  3. Verify that the OAuth configuration file contains valid values and load the correct configuration into the CLI context used by the pipeline.
  4. Confirm that cloudmanager_orgid, cloudmanager_programid, and cloudmanager_environmentid are set correctly.
  5. Run aio cloudmanager:list-programs again and confirm that it returns program information.
  6. Retry aio aem:rde:setup --show, aio aem:rde:status, or aio aem:rde:install <package.zip>. If the issue continues, contact Adobe Support and include the full CLI output.
recommendation-more-help
experience-cloud-kcs-help-kbarticles