Troubleshooting Unexpected Administrator Session Changes

Troubleshooting Unexpected Administrator Session Changes requires identifying whether the problem is in plugin visibility, target eligibility, the short-lived handoff, or the separate frontend session before changing configuration.

Diagnostic procedure

  1. Immediately check whether Joomla Shared Sessions is enabled; QCUI refuses operation when it detects that setting.
  2. Confirm the administrator and frontend are truly separate browser sessions/tabs and that another extension is not globally modifying login/session behavior.
  3. Verify session handler/database integrity and check whether custom SSO/security plugins are altering identities.
  4. End testing until the cause is known; QCUI is designed specifically not to replace the administrator identity.

Keep the layers separate

Treat this as a session-isolation issue and stop testing until Shared Sessions, SSO/security plugins, and the Joomla session handler are understood. QCUI is specifically designed to leave the administrator identity separate.

Information to preserve

Record Shared Sessions state, session handler, SSO/security extensions, and the exact sequence that changed the administrator identity. Stop further impersonation until the cause is understood.

When to escalate

If Troubleshooting Unexpected Administrator Session Changes persists after the documented layer is verified, stop creating repeated handoffs and preserve the exact error/context. A private support case should include version/state evidence but never passwords, session cookies, MFA secrets, or raw QCUI tokens.

Community Discussion

Want to compare support workflows, share practical tips, or discuss how you use this QCUI feature? Visit the QC User Impersonation Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.