Cloud Manager Git password regeneration fails when the automation user email is invalid
Cloud Manager Git automation can fail when the account used for CI/CD is tied to an IMS user with an invalid or inaccessible email address. In this situation, the user cannot complete the verification flow needed to sign in and regenerate Git credentials, so existing automation stops working when credentials expire or are replaced. The underlying issue is that Adobe-managed Git credentials are tied to IMS users rather than special system accounts. Create a new IMS user with a valid mailbox, assign the required Cloud Manager role, and generate new Git credentials from Access Repo Info.
Description description
Environment
- Adobe Experience Manager as a Cloud Service
- AEM Managed Services
- AEM Assets Essentials
Issue/Symptoms
- Automation fails to clone or push to
git.cloudmanager.adobe.com. - Git operations return authentication failures after previously working credentials stop working.
- The account used for automation cannot receive the verification code required for sign-in.
- Git credentials cannot be regenerated because the service user email inbox does not exist or cannot be accessed.
Cause
Cloud Manager Git credentials are tied to IMS users, not to special technical or system accounts. If the IMS user associated with automation has an invalid or inaccessible email address, the user cannot complete the verification flow required to sign in and regenerate the Cloud Manager Git password.
Resolution resolution
To resolve Cloud Manager Git password regeneration failures caused by an invalid automation-user email, follow these steps:
- Create a new IMS user with a valid non-personal email address and working mailbox, such as
user@example.com. - Assign the new user the required Cloud Manager role, such as
DeveloperorDeployment Manager. - Sign in to Cloud Manager with the new user.
- Open Access Repo Info and generate a new Git password for the Adobe-managed repository.
- Update the CI/CD system to use the new Git username and password.
- Test repository access again by running a clone, fetch, or push operation from automation.
- If authentication still fails, confirm that the new user can sign in to Cloud Manager and repeat the password generation step.