What Happens When the Username Does Not Exist
What Happens When the Username Does Not Exist explains the current QCUI 1.0.03 behavior and how it affects a Super User who needs to inspect the Joomla frontend as an eligible user.
Start-time behavior
QCUI loads the submitted value by exact username. If Joomla returns no user ID, no impersonation token is issued. QCUI records a denied_unknown_user audit event and redirects the administrator to Users with That username was not found.
Correct it
- Open Users → Manage.
- Find the actual account.
- Copy its Username exactly.
- Retry QCUI.
Privacy benefit
The launcher is not a general-purpose user-search/autocomplete endpoint. Account lookup remains inside Joomla’s normal Users manager.
Do not bypass Joomla account state
What Happens When the Username Does Not Exist 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
What Happens When the Username Does Not Exist 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.