Description

Aligns Feature:TwoFactorDescription with the actual Forced option label in Identity Pro Domain.Shared (previously the description said "Required" / equivalents), and fixes mistranslations of Feature:TwoFactor.Disabled that meant "disabled person" in de, fi, ru, ar, es, and hi. The same strings are mirrored into the Admin Console AbpIdentity:: and Identity:: locale keys. Not a breaking change — localization keys and values' structure are unchanged.

Related Studio PR (closing)

The earlier Studio-only attempt does not fix the Features dialog (API description comes from Domain.Shared). Closing that PR in favor of this volo change:

• #5607

After this merges, sync Admin Console locales into abp-studio rel-3.1 (manual merge for en.json / tr.json only).

Checklist

• I fully tested it as developer / designer and created unit / integration tests
• I documented it (localization resources only, no separate docs needed)
• I worked with the design team on UI/UX (no UI change beyond label text)
• I've assigned reviewer, related labels and set a milestone
• abp/admin-console/react-app changes: Studio en/tr sync to be done on rel-3.1 (not included here)

How to test it?

Open the Two Factor feature management screen in a tenant with a non-English language selected (e.g. de, fi, ru, ar, es, hi) and verify the feature description and option labels match: the description names each option exactly as the option label reads (Forced/Disabled/Optional), and "Disabled" no longer reads as "handicapped".

Notes

• Only the intended JSON keys were changed; incidental formatting churn from the JSON rewrite was cleaned up so the diffs stay minimal.
• The Admin Console locale files are generated from Domain.Shared resources and were updated by hand here to match.

🤖 Opened from a Volobox coding session

11.0.0-rc.2 12 November, 2026 No labels