Why Joomla Shared Sessions Disable All QCUI Impersonation

Why Joomla Shared Sessions Disable All QCUI Impersonation is a deliberate QCUI 1.0.03 behavior that protects administrator access, target-account safety, or the integrity of the one-time impersonation handoff.

The risk

With Joomla Shared Sessions, site and administrator identities can be tied together. Switching the site identity could also replace or destabilize the administrator identity, creating a lockout/security risk.

QCUI behavior

Start attempts are denied and audited as denied_shared_session. Frontend consume also checks the setting and refuses before identity switching.

Supported choice

Use QCUI only with Shared Sessions disabled. If your architecture requires Shared Sessions, use another support-testing method instead of bypassing this check.

Do not bypass Joomla account state

Why Joomla Shared Sessions Disable All QCUI Impersonation should be resolved through normal Joomla user/ACL administration. QCUI deliberately refuses to impersonate accounts that Joomla or QCUI currently considers unsafe/ineligible; changing database flags or handcrafting a token would remove the controls the support workflow depends on.

Do not bypass Joomla account state

Why Joomla Shared Sessions Disable All QCUI Impersonation should be resolved through normal Joomla user/ACL administration. QCUI deliberately refuses to impersonate accounts that Joomla or QCUI currently considers unsafe/ineligible; changing database flags or handcrafting a token would remove the controls the support workflow depends on.

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.