Fortiauthenticator v5.1.0 Release Notes
Fortiauthenticator v5.1.0 Release Notes
VERSION5.1.0
FORTINET DOCUMENTLIBRARY
http://docs.fortinet.com
FORTINETVIDEOGUIDE
http://video.fortinet.com
FORTINETBLOG
https://blog.fortinet.com
CUSTOMERSERVICE&SUPPORT
https://support.fortinet.com
http://cookbook.fortinet.com/how-to-work-with-fortinet-support/
FORTIGATECOOKBOOK
http://cookbook.fortinet.com
FORTINETTRAININGSERVICES
http://www.fortinet.com/training
FORTIGUARDCENTER
http://www.fortiguard.com
FORTICAST
http://forticast.fortinet.com
FEEDBACK
Email: [email protected]
11/01/2017
Revision 1
TABLEOFCONTENTS
Introduction 4
Special Notices 5
TFTP boot process 5
Monitor settings for web-based manager access 5
Before any upgrade 5
After any upgrade 5
What's New 6
Upgrade Instructions 9
Hardware & VM support 9
Image checksums 9
Upgrading from FortiAuthenticator v4.0 10
Product Integration and Support 12
Web browser support 12
FortiOS support 12
Fortinet agent support 12
Virtualization software support 13
Third party RADIUS authentication 13
Resolved Issues 14
Known Issues 18
Appendix A:FortiAuthenticator VM 20
FortiAuthenticator VM system requirements 20
FortiAuthenticator VM firmware 20
Appendix B:Maximumvalues 21
Hardware appliances 21
VMappliances 23
Introduction
This document provides a summary of new features, enhancements, support information, installation
instructions, caveats, and resolved and known issues for FortiAuthenticator 5.1.0, build 0083.
FortiAuthenticator is a User and Identity Management solution that provides Strong Authentication, Wireless
802.1X Authentication, Certificate Management, and Fortinet Single Sign-On.
http://docs.fortinet.com/fortiauthenticator/
The TFTP boot process erases all current FortiAuthenticator configuration and replaces it with the factory default
settings.
Fortinet recommends setting your monitor to a screen resolution of 1600x1200. This allows for all the objects in
the Web-based Manager to be viewed properly without need for scrolling.
Save a copy of your FortiAuthenticator unit configuration prior to upgrading. Go to System > Dashboard > Status
and select Backup/Restore >Download backup file to backup the configuration.
If you are using the Web-based Manager, clear your browser cache prior to login on the FortiAuthenticator to
ensure the Web-based Manager screens are displayed properly.
Before upgrading, review the following changes for impact to your unique deployment. Note that this list is not
exhaustive but highlights the major feature enhancements in this release.
Note that this is a patch release which fixes a few issues found in the release of 5.0.0. See Resolved Issues for
the issues addressed in this patch release.
For more detailed information, see the FortiAuthenticator 5.1.0 Administration Guide.
The post-login page for users of the Guest Portal was also similar to the Self-service's Portal page, with a menu
sidebar on the left and the selected menu page on the right. In 5.1.0, the left sidebar has been removed in the
effort to make it similar to the social login portal.
Once logged into the Guest Portal, users will have the opportunity to edit their profile (including name, email
address, phone number, and address), configure password recovery options (including a change their password,
and setup a security question), and register a FortiToken. These options can be made visible to the user or not by
configuring Post-login Services under Authentication > Guest Portals > Portals.
Note: Two-factor authentication is not supported for Guest Portal with FortiCloud.
Note that authorized groups must be first created under Authentication >User Management > User Groups,
where Type must be set to MAC , and MAC devices are selected for MAC address authorization. These can then
be referenced in the RADIUS client configuration page, where they are now mandatory.
MACdevice filtering can be enabled for anyRADIUS authentication, including Guest Portal authentication.
However, when used for Guest Portals, the FortiAuthenticator needs to know which HTTP parameter to extract
the MAC address from.You can now enter the MAC device HTTP parameter under the Authentication >Guest
Portals > Portals configuration page.
Multiple FortiAuthenticator guest portals are supported, where the FortiAuthenticator will act as the guest portal
host and RADIUS server.
Note: Two-factor authentication is not supported for Guest Portal with FortiCloud.
This can be viewed in the SAMLSP(FSSO) section under Authentication >Self-service Portal >Replacement
Messages, where login and logout replacement messages for SAML authentication can be configured. The
logout page can be accessed and configured by going to https://<FAC IP or FQDN>/saml-
auth/logout/.
Included in these settings is a successful logout replacement message, which confirms to end-users that the
logout was successful.
Note: If you wish to redirect users to another URL upon a successful logout, you can
replace specially-inserted placeholder text with the desired URL.
The following placeholder text can be found in the HTML section of SAMLSPLogout
Success Page:
<!-- For some providers it is possible to clear the SAML
iDP session just by redirecting the user directly to a
logout page. You can accomplish this by replacing the src
URL in the hidden iframe below. E.g.: Google:
https://accounts.google.com/Logout Okta:
https://yourdomain.okta.com/login/signout -->
Back up your configuration before beginning this procedure. While no data loss should
occur if the procedures below are correctly followed, it is recommended a full backup is
made before proceeding and the user will be prompted to do so as part of the upgrade
process.
This issue may be encountered when guest portals have been configured in
FortiAuthenticator prior to upgrade.
Workaround: Start from v5.0.0 (b0012), delete the guest portal configuration,
upgrade to v5.1.0 (b0083) and re-create the guest portal configuration.
l FortiAuthenticator 200D
l FortiAuthenticator 200E
l FortiAuthenticator 400C
l FortiAuthenticator 400E
l FortiAuthenticator 1000C
l FortiAuthenticator 1000D
l FortiAuthenticator 2000E
l FortiAuthenticator 3000B
l FortiAuthenticator 3000D
l FortiAuthenticator 3000E
l FortiAuthenticator VM (VMWare, Hyper-V, KVM, and Xen)
Image checksums
To verify the integrity of the firmware file, use a checksum tool to compute the firmware files MD5 checksum.
Compare it with the checksum indicated by Fortinet. If the checksums match, the file is intact.
MD5 checksums for software releases are available from Fortinet Customer Service & Support:
https://support.fortinet.com
After logging in to the web site, in the menus at the top of the page, click Download, then click Firmware Image
Checksums.
Alternatively, near the bottom of the page, click the Firmware Image Checksums button. (The button appears
only if one or more of your devices has a current support contract.) In the File Name field, enter the firmware
image file name including its extension, then click Get Checksum Code.
FortiAuthenticator 5.1.0 build 0083 officially supports upgrade from all versions of FortiAuthenticator 4.x.x.
Upgrading the FortiAuthenticator 3000D from 4.0.x to 4.1.x is not supported. The
workaround for this model is to upgrade from any 4.0.x version directly to 4.2.0 or
higher (skipping all 4.1.x versions).
Before you can install FortiAuthenticator firmware, you must download the firmware package from the
Customer Service & Support web site, then upload it from your computer to the FortiAuthenticator unit.
1. Log in to the Customer Service & Support web site at https://support.fortinet.com. In the Download section of the
page, select the Firmware Images link to download the firmware.
2. To verify the integrity of the download, go back to the Download section of the login page, then click the Firmware
Image Checksums link.
3. Log in to the FortiAuthenticator units Web-based Manager using the admin administrator account.
4. Go to System > Dashboard > Status.
5. In the System Information widget, in the Firmware Version row, select Upgrade. The Firmware Upgrade or
Downgrade dialog box opens.
6. In the Firmware section, select Choose File, and locate the upgrade package that you downloaded.
7. Select OK to upload the file to the FortiAuthenticator.
Your browser uploads the firmware file. The time required varies by the size of the file and the speed of your
network connection. When the file transfer is complete, the following message is shown:
It is recommended that a system backup is taken at this point. Once complete, click Start Upgrade.
Wait until the unpacking, upgrade and reboot process completes (usually 3-5 minutes), then refresh the page.
There is a known bug which exists in Google Chrome versions 44 and 45 where initially
the GUI loads correctly, however after some time, pages will stop loading with the
error on the chrome debug console "Failed to load resource: net::ERR_INSECURE_
RESPONSE".
This is a known issue and affects all sites using self-signed certificates and is fixed in
Google Chrome version 46. Chrome bug reference:
https://code.google.com/p/chromium/issues/detail?id=516808
To work around this issue in the meantime, use a different browser or Upgrade to the
Chrome Beta Channel.
Other web browsers may function correctly, but are not supported by Fortinet.
FortiOS support
l FortiOS v5.2.11
l FortiOS v5.4.5
l FortiOS v5.6.0
Other FortiOS versions may function correctly, but may not be supported by Fortinet.
For details of which Operating Systems are supported by each Agent, please see the Install Guides provided with
the software.
l VMware ESXi / ESX 4.0, 4.1, 5.0, 5.1, 5.5 and 6.0
l Microsoft Hyper-V 2010 and Microsoft Hyper-V 2012 R2
l Linux Kernel-based Virtual Machine (KVM) on Virtual Machine Manager and QEMU 2.5.0
l Xen Virtual Machine (for Xen HVM and AWS)
Support for HA in Active-Passive and Active-Active modes has not been confirmed on
the FortiAuthenticator for Xen VM at the time of the release.
FortiAuthenticator uses standards based RADIUS for authentication and can deliver two-factor authentication via
multiple methods for the greatest compatibility:
The resolved issues listed below may not list every bug that has been corrected with this release. For inquiries
about a particular bug, please Fortinet Customer Service & Support:
https://support.fortinet.com.
This patch release fixes the following issues found in the release of 5.0.0.
454046 Admin GUI Expanding OU node on Remote LDAP server often produces the following
error: Query failed: 'NoneType' object is not iterable.
449300 Admin GUI Set password email link expires after 1 day when creating local users from CSV
import.
449111 Admin GUI Creating new user with random password fails.
439458 Admin GUI The rad_accounting daemon doesn't restart (or reload config) when"expire
inaction accounting sessions" timeout is changed.
416807 Admin GUI The test filter viewing can't display all LDAP entries.
439841 Admin GUI Custom RADIUS dictionary does not support pre-defined attribtue values.
434426 Admin GUI Deleting a custom radius vendor returns success message stating that N
vendors have been deleted (where N = # of attributes + 1).
439629 Admin GUI Guest user creating handles the error ungracefully.
434595 Admin GUI When creating guest users fails due to invalid CSV file, the error message gets
hidden because the focus of the page changes.
439969 Admin GUI Invalid file in radius vendor creation gives Django error.
399856 Admin GUI Error message on login page should not say 'All fields are case-sensitive' since
the Username field isn't.
439465 Admin GUI Can't login to GUI after some time in FAC 5.0.
438396 Captive Portal NAS not allowed for access point's IP configured for authentication for
credentials portal.
435530 FSSO Delay in SSO session Creation (Logon Cache update) on FAC using DC Agent
Mode.
446273 FSSO Not able to retrieve Global Catalog database in "Fortigate Filtering" under
FSSO Method.
444655 FSSO SSO User Session Disappear from the SSO User Session list.
447103 FTM FAC sending token activation email after FortiCare returns error.
451454 Guest Portal Mouse over for guest portal pre/post-login services.
451448 Guest Portal Typo in log error message when Guest Portal profile is not fount.
440609 Guest Portal B0012: FAC Guest Portal Rules configuration appears incomplete.
440206 HA Enabling HA on FAC with several thousand remote LDAP users causes the
FAC to become unresponsive.
446989 HA Stale user data can interfere with LB sync or rebuild tables.
452419 RADIUS [TKT 2328649] Voice VLAN is not injected by Radius Attribute on MAB.
Authentication
435094 RADIUS FAC Version 4.3.2 Build 222 MAC Authentication Bypass does not work with
Authentication DELL Switch N-Series.
444206 RADIUS Certificate parsing fails during 802.1x authentication if there is a forward slash
Authentication in the OU.
437312 RESTAPI Random password expires immediately when local user created via REST API.
404797 RESTAPI Uncalled for Push is sent after invoking auth api call.
443935 SCEP B0226: Under lab. stress, GUI display "An error has occurred". Probable
database connection exhaustion error.
440338 SCEP B0012: SCEP enrollment doesnt work - cant generate certificate from FMG.
423286 Security Advisory: Using X-XSS-Protection HTTP secure header block reflected XSS
attacks.
408883 SMS SMS with third party vendors generates errors for other HTTP status code than
200.
452545 Usage Profile rad_accounting not starting when enabling usage profile feature.
439303 Xen VM Openvpn and message-based debug didn't work on AWS VM.
Known Issues
This section lists the known issues of this release, but is not a complete list. For inquires about a particular bug,
please contact Fortinet Customer Service & Support:
https://support.fortinet.com
457980 Firmware Firmware upgrade from 5.0 (b0012) failure if guest portals configured
Upgrade
409345 GUI When the Self-service Portal is enabled, a user (remore user) with admin access
can not log into FAC with 2factor.
448468 GUI Adding french accents in Replacement messages causes the message to display
incorrectly
452042 GUI Using IE11 to display/export the Guest user info doesn't work properly
450478 SAML IdP SAML IdP login failed for user with long DN
400466 SAML IdP SAML IDP: support signed auth request with embedded signature
451841 Windows FAC Agent service fails to start and/or disconnects after windows update
Agent
404902 Windows FortiAuthenticator Agent for MSWindows: Domain Name contains Hyphen
Agent doesn't work correctly
394402 OWA Agent OWA Agent does not work with Exchange 2016
452021 Certificate Incomplete certificate info in certificate expiration warning email message
Management
451789 FSSO RSSO not working with subdomain user via Global Catalog
450441 FSSO Secondary LDAP server is not used for RSSO group resolution
414100 RADIUS FAC losts RADIUS connection after retriving its connection between Hyber-V
FAC and it's virtual disks located on SAN.
445101 LDAP Sync LDAP sync overloads box during connectivity failure
Appendix A:FortiAuthenticator VM
The following table provides a detailed summary on FortiAuthenticator VM system requirements. Installing
FortiAuthenticator VM requires that you have already installed a supported virtual machine (VM) environment.
For details, see the Install Guide for FortiAuthenticator VM available at http://docs.fortinet.com.
VMRequirements
FortiAuthenticator VM firmware
l .out
Use this image for new and upgrades to physical appliance installations. Upgrades to existing virtual machine
installations are also distributed in this format.
l ovf.zip
Use this image for new VM installations. It contains a deployable Open Virtualization Format (OVF) virtual machine
package for initial VMware ESXi installations.
For more information see the FortiAuthenticator product datasheet available on the Fortinet web site,
http://www.fortinet.com/products/fortiauthenticator/index.html.
This section lists the maximum number of configuration objects per FortiAuthenticator appliance that can be
added to the configuration database for different FortiAuthenticator hardware and VM configurations.
The maximum values in this document are the maximum configurable values and are
not a commitment of performance.
Hardware appliances
The following table describes the maximum values set for the various hardware models.
System
SMS Gateways 20 20 20 20 20
SNMP Hosts 20 20 20 20 20
Language Files 50 50 50 50 50
Authentication
Users
500 2000 10000 20000 40000
(Local + Remote)1
Certificates
Certificate CA Certificates 10 10 50 50 50
Authorities
Trusted CA Certificates 200 200 200 200 200
1 Note that there is one metric used for the number of allowed users which is Users . Local Users and Remote
Users share the same limit value. This enables Local Users or Remote Users to be equal to Users or for there to
be a mixture of user types, however, the total number of Local and Remote Users cannot exceed the Users
metric.
2 FortiToken Mobile Licenses refers to the licenses that can be applied to a FortiAuthenticator, not the number
of FortiToken Mobile instances that can be managed. The total number is limited by the FortiToken metric.
3 For the 3000E, the total number of concurrent SSO Users is set to a higher level to cater for large
deployments.
VMappliances
The FortiAuthenticator-VM Appliance is licensed based on the total number of users and licensed on a stacking
basis. All installations must start with a FortiAuthenticator VM-Base license and users can be stacked with
upgrade licenses in blocks of 100, 1,000, 10,000 and 100,000 users. Due to the dynamic nature of this licensing
model, most other metrics are set relative to the number of licensed users. The Calculating Metric column below
shows how the feature size is calculated relative to the number of licensed users for example, on a 100 user
FortiAuthenticator-VM Base License, the number of Auth Clients (NAS Devices) that can authenticate to the
system is:
100 / 10 = 10
Where this relative system is not used e.g. for static routes, the calculating metric is denoted by a -. The
supported figures are shown for both the base VM and a 5000 user licensed VM system by way of example.
MaximumValues - VirtualMachines
Feature Model
System
SMS Gateways 2 20 20 20
SNMP Hosts 2 20 20 20
Language Files 5 50 50 50
Authentication
Group RADIUS
9 Users x 3 300 15000
Attributes
FortiToken Mobile
3 200 200 200
Licenses (Stacked) 2
Device (MAC-based
1 Users / 10 10 500
Auth.)
Feature Model
Users / 100
Domain Controllers 3 10 50
(min=10)
Users /100
FSSO Tier Nodes 3 5 50
(min=5)
Certificates
Feature Model
Certificate Revocation
5 200 200 200
Lists
1 Note that there is one metric used for the number of allowed users which is Users . Local Users and Remote
Users share the same limit value. This enables Local Users or Remote Users to be equal to Users or for there to
be a mixture of user types, however, the total number of Local and Remote Users cannot exceed the Users
metric.
2 FortiToken Mobile Licenses refers to the licenses that can be applied to a FortiAuthenticator, not the number
of FortiToken Mobile instances that can be managed. The total number is limited by the FortiToken metric.