#111354Deactivating MFA in User Settings fails with "Invalid request could not be processed
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
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 97380 status
NewUnder Review <span data-processor="relativetime" data-value="2026-11-06T06:12:58+00:00" > 11/06/26, 06:12 </span> -
Gerrit Code Review pushed patch set 1 for main to change 97393 <span data-processor="relativetime" data-value="2026-11-06T10:06:30+00:00" > 11/06/26, 10:06 </span>
-
Gerrit Code Review pushed patch set 2 for 14.3 to change 97380 <span data-processor="relativetime" data-value="2026-11-09T14:04:52+00:00" > 11/09/26, 14:04 </span>
-
Himanshu Ramavat commented and changed status
Under ReviewResolved done0 %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.