Fortiauthenticator Windows Agent v4.0 Release Notes
Fortiauthenticator Windows Agent v4.0 Release Notes
FORTINET BLOG
https://blog.fortinet.com
NSE INSTITUTE
https://training.fortinet.com
FORTIGUARD CENTER
https://www.fortiguard.com
FEEDBACK
Email: [email protected]
Change log 4
FortiAuthenticator Agent for Microsoft Windows 4.0 release 5
What's new 6
Product integration and support 7
FortiAuthenticator Support 7
Operating systems 7
Resolved issues 9
This document provides a summary of new features, enhancements, support information, installation instructions,
caveats, and resolved and known issues for FortiAuthenticator Agent for Microsoft Windows 4.0.
What's new
FortiAuthenticator Agent for Microsoft Windows version 4.0 includes the following new features and enhancements:
l A new temporary token option that allows the use of emergency codes for offline end-users who find themselves
without access to FortiToken, email, or SMS.
This feature needs FortiAuthenticator server 6.4.1 to work.
l FortiAuthenticator Agent for Microsoft Windows now allows TOTP cache sizes up to 200 days and HOTP up to 4000
logins.
This feature needs FortiAuthenticator server 6.4.1 to work.
l log4net version updated to 2.0.12.
l Short-time caching of calls to AD (for exempt groups).
FortiAuthenticator Support
FortiAuthenticator Agent for Microsoft Windows 4.0 supports the following FortiAuthenticator versions:
l FortiAuthenticator 6.4.1*
l FortiAuthenticator 6.4
l FortiAuthenticator 6.3.3
l FortiAuthenticator 6.3.2
l FortiAuthenticator 6.3.1
l FortiAuthenticator 6.3
l FortiAuthenticator 6.2.1
l FortiAuthenticator 6.2
l FortiAuthenticator 6.1
l FortiAuthenticator 6.0.7
l FortiAuthenticator 6.0.6
l FortiAuthenticator 6.0
* FortiAuthenticator 6.4.1 and above required to use emergency offline access. Also, FortiAuthenticator 6.4.0 and below
are compatible for all other features.
Operating systems
Server
Operating System
Desktop Operating
System
Resolved issues
The resolved issues listed below may not list every bug that has been corrected with this release. For inquiries about a
particular bug, please visit the Fortinet Support website.
Bug ID Description
754589 Push Service does not recognize the realm from FortiAuthenticator Agent for Microsoft Windows agent
(The feature needs FortiAuthenticator server 6.4.1 to work).
733788 Support for UPN username format in FortiAuthenticator Agent for Microsoft Windows agent (The feature
needs FortiAuthenticator server 6.4.1 to work).
710223 SMS Token code not delivered for a user with a blank password (The feature needs FortiAuthenticator
server 6.4.1 to work).
Copyright© 2021 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., and other Fortinet names herein
may also be registered and/or common law trademarks of Fortinet. All other product or company names may be trademarks of their respective owners. Performance and other metrics contained herein were
attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance
results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract,
signed by Fortinet’s General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such event, only
the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be limited to performance in the same ideal
conditions as in Fortinet’s internal lab tests. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change,
modify, transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.