Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

Special notices

TFTP boot firmware upgrade process

Upgrading FortiAuthenticator firmware by interrupting the FortiAuthenticator boot process and installing a firmware image from a TFTP server erases the current FortiAuthenticator configuration and replaces it with factory default settings.

Monitor settings for GUI access

Fortinet recommends setting your monitor to a screen resolution of 1600x1200. This allows for all the objects in the GUI to be viewed properly without the need for scrolling.

Before any firmware upgrade

Save a copy of your FortiAuthenticator configuration before upgrading the firmware. From the administrator dropdown menu in the toolbar, go to Restore/Backup, and click Download Backup File to backup the configuration.

Disable the pre-authentication warning message

Enabling the pre-authentication warning message in 6.1.0 prevents access to the GUI, therefore, the pre-authentication warning message should not be enabled in 6.1.0.

Before upgrading to FortiAuthenticator 6.1.0 (i.e. in 6.0.4), disable the option to Enable pre-authentication warning message under System > Administration > System Access.

Upgrading from FortiAuthenticator 4.x/5.x/6.0.x

FortiAuthenticator 6.1.0 build 0396 officially supports upgrade from FortiAuthenticator 6.0.4.

All other versions of FortiAuthenticator must first be upgraded to 6.0.4 before upgrading to 6.1.0, otherwise the following message will be displayed: "Image validation failed: The firmware image model number is different from the appliance's".

After any firmware upgrade

Clear your browser cache before logging in to the FortiAuthenticator GUI to ensure the pages display properly.

HA compatibility

Secondary units that are freshly installed on 6.1.0 are not compatible with Primary units that have been upgraded from 6.0.4 and earlier to 6.1.0.

As a workaround, you can downgrade the Secondary unit to 6.0.4 and then upgrade it to 6.1.0, or perform a factory reset on the Primary in the HA configuration on 6.1.0.

This compatibility issue does not exist when the Primary and Secondary units are both fresh installations in 6.1.0.

Special notices

TFTP boot firmware upgrade process

Upgrading FortiAuthenticator firmware by interrupting the FortiAuthenticator boot process and installing a firmware image from a TFTP server erases the current FortiAuthenticator configuration and replaces it with factory default settings.

Monitor settings for GUI access

Fortinet recommends setting your monitor to a screen resolution of 1600x1200. This allows for all the objects in the GUI to be viewed properly without the need for scrolling.

Before any firmware upgrade

Save a copy of your FortiAuthenticator configuration before upgrading the firmware. From the administrator dropdown menu in the toolbar, go to Restore/Backup, and click Download Backup File to backup the configuration.

Disable the pre-authentication warning message

Enabling the pre-authentication warning message in 6.1.0 prevents access to the GUI, therefore, the pre-authentication warning message should not be enabled in 6.1.0.

Before upgrading to FortiAuthenticator 6.1.0 (i.e. in 6.0.4), disable the option to Enable pre-authentication warning message under System > Administration > System Access.

Upgrading from FortiAuthenticator 4.x/5.x/6.0.x

FortiAuthenticator 6.1.0 build 0396 officially supports upgrade from FortiAuthenticator 6.0.4.

All other versions of FortiAuthenticator must first be upgraded to 6.0.4 before upgrading to 6.1.0, otherwise the following message will be displayed: "Image validation failed: The firmware image model number is different from the appliance's".

After any firmware upgrade

Clear your browser cache before logging in to the FortiAuthenticator GUI to ensure the pages display properly.

HA compatibility

Secondary units that are freshly installed on 6.1.0 are not compatible with Primary units that have been upgraded from 6.0.4 and earlier to 6.1.0.

As a workaround, you can downgrade the Secondary unit to 6.0.4 and then upgrade it to 6.1.0, or perform a factory reset on the Primary in the HA configuration on 6.1.0.

This compatibility issue does not exist when the Primary and Secondary units are both fresh installations in 6.1.0.