How it works
Multi-factor authentication (MFA) adds a step after the password: a 6-digit code that changes every 30 seconds, provided by an authenticator app installed on the user's phone (Google Authenticator, FreeOTP, Microsoft Authenticator…).
Even if a password is stolen, signing in is impossible without that code. The second factor is an open standard (TOTP, RFC 6238): no dependency on any external service.
Enable MFA (administrator)
Go to Administration → Technical configuration → Authentication → Multi-factor authentication (MFA).
Tick the levels for which the second factor must be mandatory
Super-administrator, Administrator, Trainer, Learner.
Click Save.
> No box ticked = MFA disabled on the platform. You can require MFA only for sensitive profiles (for example Super-administrator and Administrator) and leave it off for others.
What affected users experience
At their next sign-in, people whose level is subject to MFA are guided through setup:
They install an authenticator app on their phone.
They scan the QR code shown (or enter the key manually).
They enter the 6-digit code to activate.
They receive a list of backup codes to keep in a safe place.
On later sign-ins, after the password, they simply enter the code shown by the app.
If the phone is lost
Three safety nets are provided:
- Backup codes: each allows one sign-in (single use). They are shown only once at activation — keep them carefully.
- E-mail fallback: from the verification screen, the user can request a code by e-mail (valid for 10 minutes).
- If all of these are lost, an administrator can reset the account's second factor so the person enrolls again.
Key points
- SSO and LDAP are not affected: for a user who signs in via Keycloak, SAML, CAS or a directory, the second factor is handled by your identity provider, not by DGTLMS.
- Each user's secret is encrypted in the database; it is never stored in clear text.
- MFA applies to username-and-password sign-ins (including the automatic "stay signed in" cookie).