I’ve been testing MFA (TOTP) integration in my OpenZiti deployment and noticed some confusing behavior when enforcing TOTP in the default authentication policy.
Currently, I can manually enable MFA for each identity, which works fine—but with around 100–200 users, managing MFA individually becomes impractical.
To streamline this, I tried enabling TOTP MFA enforcement in the default authentication policy so that new identities are automatically required to use MFA during enrollment. However, when a new user enrolls, the Ziti Desktop Edge client skips the QR code or secret key display step and directly prompts for a TOTP code.
At that point, the user has no prior secret or authenticator app configured, so they’re effectively stuck.
Could you please clarify whether this is
-
The intended behavior (by design),
-
A known issue or bug, or
-
Is there any recommended workaround to enforce MFA automatically but still allow users to see the QR code for initial setup?
-
Also I dont see any option to implement MFA for Ziti mobile client
The goal is to have new users automatically prompted to set up MFA during their first enrollment—without needing per-user manual intervention.
