Technical Tip: Enabling Multi-VDOM resources Access for SSL VPN users

[ManpreetSingh]

Description	This article describes how to allow SSL VPN users terminated on WAN PORT/PORT9 VDOM_A to access the File server connected to port 5 on VDOM_B.
Scope	FortiGate.
Solution	To make this work, follow these steps: Setup SSL VPN on VDOM_A: Setup SSL VPN portal on VDOM_A and add the subnet of the file server from VDOM_B to the routing override address along with the desired local LAN subnet.                                Setting up SSL VPN in VDOM_A: Designate the interface on VDOM_A that will handle SSL VPN traffic. In this scenario, configure Port 9 as the WAN interface to listen for SSL VPN connections. Routing configuration at VDOM_A: Ensure static routes or appropriate dynamic routing protocols are configured to connect the VDOMs and allow traffic flow between them VDOM_A must have the routes to the file server behind VDOM_B pointing towards the inter-VDOM link. Static Routing Configuration at VDOM_B:  VDOM_B must have the SSL VPN subnet in its routing table pointing towards the inter-VDOM link. In VDOM_B, add a static route for the SSL VPN client subnet, directing it towards the inter-VDOM link. Firewall policy on VDOM_A: VDOM_A must have a firewall policy to allow the SSL VPN subnet and user group to access File Sever in VDOM_B through an inter-VDOM link. Specify the user group to which the SSL VPN user belongs.   Firewall policy on VDOM_B: VDOM_B must have a firewall policy to allow incoming traffic from the SSL VPN subnet of VDOM_A to access the File server on Port 6. Here the incoming interface should be the inter-VDOM link.