I’m pretty much at my wits end. We recently deployed a Fortigate cluster to replace some old stuff and get MFA for SSL VPN via Entra ID set up.
There was of course research and planning involved, so Fortinet EMS as cloud version was licensed.
These past days I tried setting it all up, once I’m logged into windows everything works perfectly fine… but connecting the VPN before logging into Windows, something we’d like to do for several reasons (mainly Kerberos since gpos will be phased out in favor of autopilot) just won’t work.
I tried FCT 7.0.9 and even 7.2.2 on Windows 10 and 11 on-prem AD joined, autopilot joined and even fresh out of the box as stand-alone. I did install via msi + mst. Enable vpn before logon is enabled in the EMS profile and the correct profile was deployed and is applied.
But none of those 6 machines allows me to connect to vpn before signing into windows. I don’t even get the “sign in options”… I looked at any documentation I could find and read several threads in this sub. It seems EMS should be the solution, but it just won’t work for me.
I have opened a ticket with Fortinet since it won’t even work on an untouched device fresh from the manufacturer, but maybe someone on here has some hints?
TL;DR:
-FortiClient EMS cloud licensed
-“enable vpn before login” in EMS portal is set and applied
-“sign in options” not available on several different W10/W11 devices
for time travelleres, so yeah 7.0.13 is fucked, dropped external browser saml and went down to 7.0.3 that works as expected, saml on desktop but normal SBL on login screen. with that should be officially supported for ems 7.2.x. also no clue how fortinet plans on implementing saml on sbl, probably a pipe dream.
Not really. When I create a custom/personal connection on the PC it shows up. But not my other profiles.
All my production profiles use SAML. Could it be that authentication methods not supported are not showing up at the Windows login screen? I could see them when we used 6.4.9 but not in 7.0.
Our vpn interface has a few local users configured besides the saml-group. Vpn before logon works for those, but as another commenter hinted, you can only do saml on logon on fortiOS 7.2, but not before. Still, the pre-logon vpn is present on 7.0.3 but disappears on 7.0.10.
I guess we’ll have to live with that for now. Not perfect, but not the worst either.
According to this, since 7.0.7, although I wouldn’t consider it SBL, more like SOL?
Once 7.2.1+ becomes mature, I’ll give it a try. For now, manually establishing the vpn after logon works fine for us, since the devices are AAD only joined and receive the Kerberos ticket pretty much as soon as the user connects to vpn.
That already worked on 7.0.3 if you checked the “keep me signed in” box. The frequency of MFA challenges needs to be configured through conditional access policies in Entra.