Product integration and support

Web browser support

The following web browsers are supported by FortiProxy 2.0.12:

• Microsoft Edge

• Mozilla Firefox version 61

• Google Chrome version 67

Other web browsers might function correctly but are not supported by Fortinet.

Fortinet product support

• FortiOS 5.x and 6.0 to support the WCCP content server

• FortiOS 5.6.3 and 6.0 to support the web cache collaboration storage cluster

• FortiAnalyzer 5.6.5

• FortiSandbox and FortiCloud FortiSandbox, 2.5.1

Software upgrade path

FortiProxy supports upgrading directly from 1.0.x, 1.1.x, 1.2.x, or 2.0.x to 2.0.10.

Fortinet Single Sign-On (FSSO) support

• 5.0 build 0295 and later (needed for FSSO agent support OU in group filters)

  • Windows Server 2019 Standard

  • Windows Server 2019 Datacenter

  • Windows Server 2019 Core

  • Windows Server 2016 Datacenter

  • Windows Server 2016 Standard

  • Windows Server 2016 Core

  • Windows Server 2012 Standard

  • Windows Server 2012 R2 Standard

  • Windows Server 2012 Core

  • Windows Server 2008 64-bit (requires Microsoft SHA2 support package)

  • Windows Server 2008 R2 64-bit (requires Microsoft SHA2 support package)

  • Windows Server 2008 Core (requires Microsoft SHA2 support package)

  • Novell eDirectory 8.8

Virtualization environment support

Fortinet recommends running the FortiProxy VM with 4+ GB memory because the AI-based Image Analyzer uses more memory comparing to the previous version.

HyperV	Hyper-V Server 2008 R2, 2012, 2012R2, 2016, and 2019
Linux KVM	RHEL 7.1/Ubuntu 12.04 and later CentOS 6.4 (qemu 0.12.1) and later
Xen hypervisor	OpenXen 4.13 hypervisor and later Citrix Hypervisor 7 and later
VMware	ESXi versions 6.0, 6.5, 6.7, and 7.0
Openstack	Ussuri

New deployment of the FortiProxy VM

The minimum memory size for the FortiProxy VM for 2.0.12 or later is 4 GB. You must have at least 4 GB of memory to allocate to the FortiProxy VM from the VM host.

Upgrading the FortiProxy VM

If you are upgrading from FortiProxy 1.1.2 or earlier, including FortiProxy 1.0 to FortiProxy 2.0.12 or later, use the following procedure:

1. Back up the configuration from the GUI or CLI. Make sure the VM license file is stored on the PC or FTP or TFTP server.

2. Shut down the original VM.

3. Deploy the new VM. Make sure that there is at least 4 GB of memory to allocate to the VM.

4. From the VM console, configure the interface, routing, and DNS for GUI or CLI access to the new VM and its access to FortiGuard.

5. Upload the VM license file using the GUI or CLI

6. Restore the configuration using the CLI or GUI.

Downgrading the FortiProxy VM

Do not downgrade the FortiProxy VM 2.0.6 because the new VM license file cannot be used by earlier versions of FortiProxy.

If you are downgrading from FortiProxy 2.0.5 to FortiProxy 1.1.2 or earlier, use the following procedure:

1. Back up the configuration from the GUI or CLI. Make sure the VM license file is stored on the PC or FTP or TFTP server.

2. Shut down the original VM.

3. Deploy the new VM. Make sure that there is at least 2 GB of memory to allocate to the VM.

4. From the VM console, configure the interface, routing, and DNS for GUI or CLI access to the new VM and its access to FortiGuard.

5. Upload the VM license file using the GUI or CLI

6. Restore the configuration using the CLI or GUI.