Technical Tip: Migrating an application from VPN IPsec client-to-site to ZTNA.

[agomes]

Description	This article shows how to move an application from a VPN IPsec client-to-site to ZTNA.
Scope	FortiGate, FortiClient EMS, and FortiClient.
Solution	Follow these to move the application from VPN IPsec client-to-site to ZTNA Application with FortiClient EMS. This procedure needs a fabric configuration between FortiGate and FortiClient EMS. If a FortiManager application is accessible through a VPN IPsec client-to-site, the following configuration will involve a VPN and a policy allowing the respective traffic. The topology below illustrates the VPN IPsec client-to-site traffic flow. Follow the ZTNA traffic flow: To move this configuration to ZTNA, follow these steps: Create a ZTNA Server on the FortiGate. Use the FortiGate interface address that the client will connect to access the application (proxy address). Try to use a different port from the management port. Map the application using TCP Forwarding and insert the port that the application will be accessible on. Go to the FortiClient EMS server and check if the application was synced with the fabric on Fabric Connectors -> ZTNA Application Catalog. See the screenshot below. Go to the ZTNA Destination profile, select the add button in the Rules Grouped by ZTNA Applications tab, choose the application, and select the Finish button to sync this application with the FortiClient. Select the Save button to save the profile and sync this application with the FortiClient. Check on the FortiClient if the application was synced. Go to the FortiGate and create a ZTNA policy to allow this traffic. The use of security posture tags can be used if necessary to restrict access as well, but this article does not cover security posture tags. After this, try to access the application through its original IP address https://172.16.1.100. FortiClient will use the FortiGate (192.168.50.1:4443) as a proxy and access the Application.