Upgraded by development 200B. Seems to have gone smooth.
The release notes talk about rebuilding the reports and the reports DB. It provides the two commands to run to accomplish this. However the " execute report recreate-db" command fails. Opened a ticket with fortinet about this, let see what they say.
Also once again Fortinet has not posted the MSI file for the SSLVPN client.
Thankfully you can extract the MSI out of the EXE, by running the EXE and grabbing the MSI file out of your temp folder before the install completes.
It seems to me that Fortinet changed the way FW Policies with authentication works. Now the URL of the Portal is not longer the URL the user used to connect but the IP of the Fortigate. Of course this leads to certificate Problems...
Hi , I have not tested 5.0.8 .
But in 5.2 ,they have moved the option ( Captive portal) to interface.
And if you don' t want to use the Captive portal in any of the policies.
you can use " set captive-portal-exempt disable"
As it turns out the issue was my " Access Point Isolation" settings that I have on my Unifi Wifi Access points. The fortinet change to use Interface IP address cause the Wifi units to block it.
As soon as I put an exception in, the captive portal started working again.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.