Documentation

Login failure for a specific user in AEM production environment

Last update: Mon May 25 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Login fails in the Adobe Experience Manager as a Cloud Service (AEMaaCS) production environment even though correct product profiles are assigned. The system displays an access restriction message and redirects to the landing page. Login works in lower environments but fails only in production, indicating an environment-specific access issue. To resolve the issue, verify access settings, approve requests, and review logs carefully.

Description description

Environment

  • Product: Adobe Experience Manager as a Cloud Service (AEMaaCS) – Assets, v6.5
  • Environment type: Production (author tier)
  • Product Offering: Cloud Manager

Issue/Symptoms

  • A user is unable to log in to the AEM production author instance.
  • The message displayed is: You don’t have access to the instance and have been redirected to the landing page.
  • Login works for this user in development and staging environments, but not in production.
  • The affected user is assigned to both AEM Users and AEM Administrator product profiles.
  • AEM logs show authentication failure with Login Failure: all modules ignored.

Resolution resolution

Follow the steps below to address the issue:

  1. Verify that the affected account includes both AEM Users and AEM Administrator product profiles for the production environment in Admin Console.
  2. Check for any pending impersonation requests associated with the account and approve them where applicable to ensure access propagates correctly.
  3. Review recent synchronization or onboarding activities in the Admin Console and confirm that profile assignments sync correctly with the production environment.
  4. Collect relevant AEM authentication logs that show “Login Failure: all modules ignored” and validate whether the system correctly recognizes assigned profiles.
  5. Compare access behavior across other accounts to confirm whether the issue remains isolated or affects multiple accounts, then escalate with collected logs if required.

Note: The issue remains isolated to a single account in production. Development and staging environments remain unaffected. As of now, no confirmed root cause or final resolution steps are available.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f