Skip to main content

2. What's New

v3.0.1

Security

  • While a user waits for the code, the session no longer counts as signed in for anything that reads it, such as the REST API session token or the API authorisation endpoint — see 5.1.1.1 The code form
  • The sign-in methods that use only the password and never reach the code form are refused for the accounts that need a code: CalDAV, the REST API login with password and the OAuth password grant
  • A second factor enrolled during the sign-in itself, in the native 2FA setup step, no longer waives the code: only one that existed before the sign-in does

New

  • The settings cannot turn a type on while codes cannot be delivered (notifications off, notification inactive or the queue action disabled), and warn when a saved setting would lock users out — see 4.1.1 The warning in the MFA tab
  • The code form tells the user when the mail server refused the code, and reloading it tries again
  • A new switch for CAS and x509 accounts, which were never asked for a code — see 4.5.2 Turn the types on
  • A new install starts with every type set to No

Fixed

  • The code form is shown in normal mode, without the debug bar, while a code is pending
  • Sessions opened before the plugin was activated are no longer sent to the code form right after activating it
  • The page requested before the code is kept relative to the GLPI root, so the redirection also works when GLPI is in a sub-directory
  • The automatic action is registered at install time, not on every request

Generated for MFA 3.0.1 on GLPI 12.0.2 — 2026-11-20.