DocumentationExperience Cloud KCS

Resolving Cloud Manager Git authentication failures from expired or cached credentials

Last update: August 18, 2026

Authentication to Cloud Manager Git repositories fails during push, clone, or automated CI/CD sync when the Git password has expired, the wrong Git username or password is used, or local and CI systems are still using outdated cached credentials. Cloud Manager Git requires a Git-specific username and password generated in the Access Repo Info panel, so SSO or Adobe ID credentials don’t work, and a regenerated password invalidates the previous one immediately. Regenerating the Git password, clearing cached credentials, and updating CI secrets restores authentication across AEMaaCS and AMS environments.

Description description

Environment:

  • Adobe Experience Manager as a Cloud Service (AEMaaCS)
  • AEM Managed Services (AMS)
  • Cloud Manager Git repositories
  • CI/CD systems (Bitbucket, GitHub Actions, Azure DevOps) and local developer machines

Issue/Symptoms:

  • Git fails with fatal: Authentication failed for the Cloud Manager repository URL.
  • Git fails with fatal: cannot prompt because user interactivity has been disabled.
  • Git fails with fatal: could not read Username … No such device or address.
  • Pipeline jobs fail at the push-to-AEM step.

Root cause:

Cloud Manager Git access credentials consist of a Git username and a password generated through the Access Repo Info panel. These passwords expire (typically after one year) or are invalidated immediately when a new password is regenerated. CI/CD systems and developer machines that continue using an old cached password produce non-interactive authentication failures. SSO and Adobe ID credentials don’t work, because Cloud Manager Git requires the Git-specific username and password.

How to confirm

  1. Confirm the Git username for the repository. In Cloud Manager, go to Program → Pipelines → Access Repo Info → View Repo Info and note the displayed repository URL and Git username. Confirm the username matches what your Git command or CI variables use; a mismatch is a common cause.
  2. Capture the exact Git error to confirm it’s credential-related. Authentication failed indicates a password mismatch, and cannot prompt because user interactivity has been disabled indicates CI is running in non-interactive mode with stale credentials.

Resolution resolution

  1. Regenerate the Git password. In the Repo Info dialog, click Generate Password and copy the password immediately, then store it in your secure secret store or local environment. The previous password becomes invalid immediately. If the button doesn’t appear, your account doesn’t have Cloud Manager access — contact your program admin.
  2. Remove cached or outdated credentials on local machines. On macOS, open Keychain Access, search for the Cloud Manager Git host, and delete the entry. On Windows, open Credential Manager → Windows Credentials and remove the entries for the Cloud Manager Git host. Re-run git fetch or git clone and confirm Git prompts for new credentials. If no prompt appears, run the operation from a clean directory or reset the Git credential helper configuration.
  3. Test authentication from a terminal before updating CI/CD systems. Run git ls-remote https://git.cloudmanager.adobe.com/<org>/<repo> and enter the Git username and the newly generated password when prompted. The command lists the remote branch references (such as refs/heads/main) on success.
  4. Update CI/CD systems with the new credentials. Update the CI secrets that store the Git username and password in each system you use (Bitbucket, GitHub Actions, Azure DevOps, or internal pipelines), then re-run the job and confirm the push to Cloud Manager succeeds. If it still fails, enable verbose Git logging with GIT_TRACE=1 and GIT_CURL_VERBOSE=1 and collect the output.
  5. If a service account is used and the credentials are unknown, log in to the Adobe ID of the service account to open Access Repo Info and generate a new Git password. If you can’t access the account, you can’t regenerate its credentials — create a new user or convert the pipeline to use the Cloud Manager APIs instead.

Validation

  1. Run git ls-remote https://git.cloudmanager.adobe.com/<org>/<repo> with the new credentials and confirm it lists the remote refs.
  2. Re-run the affected pipeline and confirm it passes the push-to-AEM or code-quality step without authentication errors.
recommendation-more-help
experience-cloud-kcs-help-kbarticles