Troubleshooting a Password-Reset-Required Target User

Troubleshooting a Password-Reset-Required Target User 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. Open the target user in Joomla Users.
  2. Confirm the account is flagged to require password reset.
  3. Complete or administratively resolve the required reset through the normal Joomla account process.
  4. After the reset-required flag is cleared, create a fresh QCUI handoff.

Keep the layers separate

This is an intentional credential-state denial. Complete the required Joomla password-reset workflow first; QCUI should not be used to bypass requireReset.

Information to preserve

Record the target username and whether Joomla currently requires a password reset. Do not send the old/new password or MFA data.

When to escalate

If Troubleshooting a Password-Reset-Required Target User 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.

When to escalate

If Troubleshooting a Password-Reset-Required Target User 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.