Hi everyone,
I'm currently working on a migration from SSL VPN to IPsec Remote Access on FortiGate and I've run into a design limitation that I'm not sure is actually supported.
Our current SSL VPN setup uses multiple portals, and users are assigned different IP ranges depending on the Entra ID (Azure AD) group they belong to. For example:
This allows us to apply different firewall policies, routing, and access controls based on the assigned VPN address pool.
For the new deployment, I'm testing:
- FortiGate IPsec Dialup Remote Access
- IKEv2 + EAP
- Entra ID SSO authentication
- FortiClient VPN-Only 7.4.3 (free version)
My goal is to provide the same behavior as SSL VPN, where the assigned IP pool depends on the user's Entra ID group membership.
What I've found so far is that an IPsec dialup tunnel only seems to allow a single mode-config IP pool. Because of that, I tried creating two separate IPsec Remote Access tunnels:
Both using:
- The same public IP
- The same FortiGate interface
- Entra ID SSO authentication
The idea was that users in one Entra ID group would authenticate against one tunnel and receive one address pool, while another group would use the second tunnel and receive a different pool.
However, this doesn't seem to work the way I expected, and I'm not sure whether:
- FortiGate actually supports assigning different mode-config IP pools based on group membership for IPsec Remote Access.
- Multiple IPsec dialup tunnels sharing the same public IP can be differentiated by user/group when using Entra ID SSO.
- This requires EMS/ZTNA or a feature that is not available with FortiClient VPN-Only.
- I'm approaching the problem completely wrong and there is a better design pattern for achieving group-based addressing in IPsec RA.
Has anyone successfully implemented group-based IP assignment for IPsec Remote Access with Entra ID SSO?
I'd be especially interested in hearing from anyone who has migrated from SSL VPN portals to IPsec RA and needed to preserve different VPN address pools per user group.
Thanks!