I have been working on a split-routed SSL VPN configuration using SAML/SSO authentication. The authentication part seems to work, but I have noticed that using FortiClient VPN 7.0.* for Windows (e.g. 7.0.2.0090), most times one or more static routes do not get set up. After some experimenting I have discovered that this seems to be confined to FortiClient VPN 7.0.*; using FortiClient VPN 6.4.* (e.g. 22.214.171.1245) it all seems to work fine with all the routes added to the Windows route table every time.
Has anyone else noticed this? Is there a solution, or even the expectation of a fix?
I've noticed this issue in our environment too. It doesn't appear to happen on our Windows 10 laptops, but it does appear to happen on older versions of Windows. I haven't created a ticket for the issue yet. Did you ultimately find a resolution?
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.