NAV
AD FS MFA Plugin
v1.1.68 (2026-11-17)
- Important security fixes, recommended for all installations
- The status of the authentication request is checked by the AD FS server. The sign-in page no longer calls the Notakey API from the browser
- The Content-Security-Policy header of AD FS does not have to be changed on Windows Server 2019 and later, see the manual for restoring the default
- A single failed status check does not end the sign-in; failed checks are written to the event log as warnings
- Sign-ins of different users no longer share the state of the sign-in page
- The sign-in page does not load jQuery
- The uninstall script removes only the Notakey provider and keeps other additional authentication providers of the farm
- The install script upgrades an installed version without uninstalling and can be run on secondary servers of a farm
- The install script creates the event log source of the plugin and asks before it registers a new version in a farm
- The sign-in page shows an error code only; the cause is in the event log entry with the same code
- In an AD FS farm, upgrade in the order given in the manual: the new version on the secondary servers first, then on the primary server. A server that does not have the registered version does not ask for the second factor
v1.1.67 (2023-04-13)
- Add additional debug information if MFA status query fails
- Attempt to verify auth request even if no status progress can be loaded
v1.1.47 (2022-03-21)
- Do not use session fingerprinting when creating auth requests
- Update Notakey.SDK to 1.1.55
- Do not ship with Identity Server (AD FS) builtin libraries
v1.1.18 (2022-03-21)
- Add claim for support of Azure AD
v1.1.12 (2019-02-14)
- Remove http://schemas.microsoft.com/claims/authnmethodsreferences) claim