Resolve 403 Forbidden errors during BYOGIT setup for Edge Delivery Services sites created via Cloud Manager
The article addresses 403 Forbidden errors that occur during Bring Your Own Git (BYOGIT) setup for Edge Delivery Services sites created using Cloud Manager one-click site creation because no Configuration Service admin is automatically assigned. This prevents completion of the BYOGIT setup and connection of an external Git repository for code synchronization. To resolve the issue, update and validate access tokens, verify IP allowlisting, and confirm repository connectivity.
Description description
Environment
Adobe Experience Manager Edge Delivery Services (all versions)
Issue/Symptoms
- POST requests to configuration endpoints, such as
/config/[ org] /sites/[ site] /code.jsonand/secrets/cm-byog.json, return HTTP 403 Forbidden authorization errors. - GET requests to site-level and organization-level configuration endpoints return HTTP 403 Forbidden errors.
- Other services accept the same Adobe IMS tokens without issue.
Cause
Sites created via Cloud Manager one-click do not automatically assign a Configuration Service admin, resulting in a permissions gap that blocks BYOGIT setup and code synchronization until access tokens are rotated and validated.
Resolution resolution
Follow the steps below to resolve the issue.
-
Generate a new personal access token in your Git provider (for example, GitLab). Refer to your Git provider’s documentation for instructions on creating a token with the required scopes.
-
Update the token in Cloud Manager:
- Log in to Cloud Manager and select your organization.
- From the My Programs console, select the relevant program.
- In the side menu under Program, click Repositories.
- Click Manage Access Tokens in the upper-right corner.
- Edit the relevant token, enter the new value, and save.
-
Ensure that all required Cloud Manager IP addresses are allowlisted in your Git provider to permit access from Cloud Manager to your external repository. Refer to your Git provider’s documentation for allowlisting instructions.
-
Verify that Cloud Manager can connect to the external repository and that code synchronization succeeds.
Note:
- All associated repositories are revalidated after the token is updated.
- If you continue to receive HTTP 403 Forbidden errors after completing these steps, a Configuration Service admin may need to be assigned for your site.