What’s new in FortiOS 5.4

Whats new in FortiOS 5.4


Significant SSL VPN web portal improvements (287328, 292726, 299319)

Significant updates and improvements have been made to the SSL VPN web portal in preparation for future browser updates, and in order to support all browsers:

  • SSL VPN web portal redesigned.
  • SSL VPN tunnel mode widget no longer works in the web portal.The tunnel mode widget used a deprecated NPAPI plugin mechanism to send the tunnel client to the browser for local system execution—this is a popular exploitation vector. FortiClient is now required for tunnel mode SSL VPN.
  • SSL VPN Web mode RDP Native java applet removed.
  • Removed unnecessary options from RDP bookmark and changed to HTML5 RDP.
  • Cache cleaning function has been removed.


Implement post-authentication CSRF protection in SSL VPN web mode (287180)

This attribute can enable/disable verification of a referer in the HTTP request header in order to prevent a Cross- Site Request Forgery attack.



config vpn ssl settings

set check-referer [enable|disable]



Groupbased SSL VPN bookmarks (292125)

This CLI-only feature allows administrators to add bookmarks for groups of users. SSL VPN will only output the matched group-name entry to the client.



config vpn ssl web portal edit “portal-name”

set user-group-bookmark enable*/disable next


config vpn ssl web user-group-bookmark edit “group-name”

config bookmark edit “bookmark1”

…. next

end next



DTLS support (227138)

The Datagram Transport Layer Security (DTLS) protocol is supported for SSL VPN connections. DTLS support can be enabled in the CLI as described below.



config vpn ssl settings

set dtls-tunnel [enable | disable] (default: enabled)




Added options to allow firewall addresses to be used in routing table for SSL VPN (265430)

If destination Named Address is set in Network > Static Routes and Address Range is set to Automatically assign addresses in VPN > SSL-VPN Settings, SSL VPN should refresh the routing table automatically.


HTTP to HTTPS redirect support (278728)

The admin HTTP port can now be redirected to the admin HTTPS port. This is enabled in VPN > SSL- VPN Settings using the option Redirect port 80 to this login port.


There are two likely scenarios for this:

  • SSL VPN is not in use, in which case the admin GUI runs on port 443 or 10443, and port 80 is redirected.
  • SSL VPN runs on port 443, in which case port 80 is redirected to 443 and the admin port runs on 10443. If the administrator chooses to run SSL VPN on port 80, the redirect option is invalid.

This can also be configured in the CLI as described below.



config vpn ssl settings

set https-redirect [enable | disable] (default: disabled)




Removed guest group and SSO group (303041)

Guest group and SSO group have been removed from config user group and config vpn ssl web user-group-bookmark.


CLI changes (299319)

Removed the following obsolete/unnecessary portal options from the CLI:

config vpn ssl web portal edit <name>

set auto-prompt-mobile-user-download  REMOVED

set display-forticlient-download  REMOVED

set display-history-limit  REMOVED

set page-layout  REMOVED

set cache-cleaner  REMOVED

end end


Removed the following unnecessary RDP bookmark options from the CLI in preparation for HTML5 RDP:

config vpn ssl web <user-bookmark|user-group-bookmark>

edit <group/user name>

config bookmarks edit <bookmark>

set full-screen-mode  REMOVED

set screen-height  REMOVED

set screen-width  REMOVED

set keyboard-layout  REMOVED

end end

end end

2 thoughts on “What’s new in FortiOS 5.4

  1. larminaux


    I am somewhat novice on the Fortinet hardware, I would have a question:

    I currently have a basic configuration file in 5.2 with our default values, ready to be integrated into a Fortigate and to be configured in more detail later. Is file compatible with version 5.4? Or are there parameters to change to make it compatible?

    Have a good day !

    1. Mike Post author


      I would load the config on the same Gate running 5.2 code and then upgrade the firmware so it goes through the conversion process. Then you can make a backup of that configuration and be able to port it to other Gates running 5.4. Whatever you do, make sure you follow the supported upgrade path so you don’t lose any conversion processes along the way. These things behave badly when a proper step is skipped.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.