DocumentationExperience Cloud KCS

AEM Desktop App login and access failures due to IMS or SSO issues

Last update: June 27, 2026

Adobe Experience Manager (AEM) Desktop App fails to authenticate and displays blank SSO screens, access errors, or repeated login prompts. To resolve the issue, clear cache, verify connectivity, test devices, and update application.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service (AEMaaCS)
  • AEM Managed Services
  • AEM On-Premise environments using AEM Desktop App

Issue/Symptoms

  • Display the error: User does not have access to the target Adobe Experience Manager instance.
  • Show a blank or white SSO authentication screen during the login flow.
  • Fail IMS authentication with the error: request to https://ims-na1.adobelogin.com/ims/token/v3 failed, reason: connect ETIMEDOUT.
  • Fail to sign in or show repeated login prompts after upgrading the Desktop App.
  • Fail to load or display the SSO popup during authentication.

Root cause

Authentication failures occur when the AEM Desktop App cannot establish or maintain a valid authentication session with IMS endpoints or handle login flows correctly. This condition occurs due to restricted network access, stale session cache, unsupported authentication methods, device-specific issues, or application version inconsistencies that affect authentication behavior.

Resolution resolution

Follow these steps to identify the failure pattern and restore authentication successfully:

  1. Identify the login failure pattern by comparing observed behavior with scenarios such as network timeout, cached session issues, unsupported authentication, device-specific behavior, or version-related issues.
  2. Clear session cache by signing out completely, removing browser cache and cookies, and restarting the AEM Desktop App to initiate a fresh authentication flow.
  3. Validate network connectivity by testing access to the authentication endpoint over port 443 and ensuring the connection completes without timeout, and unblock traffic if required.
  4. Test authentication on another device by attempting login from a different workstation to determine whether the issue is system-specific.
  5. Verify the Desktop App version by checking the installed version and upgrading if the version is affected by known authentication or sign-in defects.
  6. Identify version-related behavior by recognizing repeated login prompts after explicit sign-out as expected behavior in certain versions.
  7. Resolve installation issues on macOS ARM devices by retransferring the installer using a direct method when authentication screens appear blank.
  8. Align the authentication method by switching to a supported sign-in type if the current method is not supported.
  9. Validate the resolution by confirming successful login, ensuring the authentication screen loads correctly, and verifying that authentication failures do not recur.

When to escalate:

  • The authentication still fails after verifying connectivity and completing all resolution steps.
  • The authentication screen remains blank after multiple retry attempts.
  • The login issues persist after clearing the cache, testing devices, and validating the application version.
  • The required authentication method is unsupported and cannot be adjusted.
recommendation-more-help
experience-cloud-kcs-help-kbarticles