Issue Bug Resolved

#111354Deactivating MFA in User Settings fails with "Invalid request could not be processed

Himanshu Ramavat 11/06/26, 06:07 updated 11/09/26, 14:10

Description

User Settings > Multi-factor authentication shows “Deactivate multi-factor authentication” after a provider such as TOTP is active.

Confirming that button posts action=deactivate to ajax/mfa with tableName=be_users_settings. MfaAjaxController only accepts be_users and fe_users, so the request is rejected with “Invalid request could not be processed” and no provider is deactivated.

be_users_settings is the FormEngine pseudo-table for User Settings. The button script must send the real table be_users, the same way SetupModuleController writes those fields back to be_users. Deactivation from the backend user record (tableName=be_users) is unaffected.

Reproduced on 14.3.11-dev. The same table name is passed on main.

Reviews 2

Files 1

History 14

  1. Himanshu Ramavat commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-09T14:10:14+00:00" > 11/09/26, 14:10 </span>

    Applied in changeset commit:0036d8a4983cd159d33950269729232ff3c769f7.