Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

Related Videos

sidebar video

Provisioning ZTNA TCP forwarding rules via EMS

  • 293 views
  • 2 months ago

EMS Administration Guide

ZTNA Connection Rules

You can use FortiClient to create a secure encrypted connection to protected applications without using VPN. Acting as a local proxy gateway, FortiClient works with the FortiGate application proxy feature to create a secure connection via HTTPS using a certificate received from EMS that includes the FortiClient UID. The FortiGate retrieves the UID to identify the device and check other endpoint information that EMS provides to the FortiGate, which can include other identity and posture information. The FortiGate allows or denies the access as applicable. See the FortiOS Administration Guide for FortiOS configuration requirements. For TCP forwarding to non-web-based applications, you must define ZTNA connection rules as follows.

You an configure these rules in a ZTNA Connection Rules profile in EMS to deploy to endpoints as part of an endpoint policy.

To add a ZTNA connection rule:
  1. Go to Endpoint Profiles > ZTNA Connection Rules.
  2. Click Add Rule.
  3. In the Rule Name field, enter the desired name.
  4. In the Destination Host field, enter the IP address/FQDN and port of the destination host in the format <IP address or FQDN>:<port>. This example enters demo.fortinet.com:22 as the destination host value.
  5. In the Proxy Gateway field, enter the FortiGate access IP address and port in the same format. This example enters 21.14.22.11:80 as the proxy gateway value.
  6. From the Mode dropdown list, select Transparent.
  7. Enable or disable encryption. By default, encryption is disabled. When encryption is enabled, traffic between FortiClient and the FortiGate is always encrypted, even if the original traffic has already been encrypted. When encryption is disabled, traffic between FortiClient and the FortiGate is not encrypted.
  8. Enable or disable User External Browser as User-agent for Saml User Authentication. When this feature is enabled, FortiClient presents a SAML authentication request to the end user in a web browser for traffic that is eligible for this rule.
  9. Click Save.

Related Videos

sidebar video

Provisioning ZTNA TCP forwarding rules via EMS

  • 293 views
  • 2 months ago

ZTNA Connection Rules

You can use FortiClient to create a secure encrypted connection to protected applications without using VPN. Acting as a local proxy gateway, FortiClient works with the FortiGate application proxy feature to create a secure connection via HTTPS using a certificate received from EMS that includes the FortiClient UID. The FortiGate retrieves the UID to identify the device and check other endpoint information that EMS provides to the FortiGate, which can include other identity and posture information. The FortiGate allows or denies the access as applicable. See the FortiOS Administration Guide for FortiOS configuration requirements. For TCP forwarding to non-web-based applications, you must define ZTNA connection rules as follows.

You an configure these rules in a ZTNA Connection Rules profile in EMS to deploy to endpoints as part of an endpoint policy.

To add a ZTNA connection rule:
  1. Go to Endpoint Profiles > ZTNA Connection Rules.
  2. Click Add Rule.
  3. In the Rule Name field, enter the desired name.
  4. In the Destination Host field, enter the IP address/FQDN and port of the destination host in the format <IP address or FQDN>:<port>. This example enters demo.fortinet.com:22 as the destination host value.
  5. In the Proxy Gateway field, enter the FortiGate access IP address and port in the same format. This example enters 21.14.22.11:80 as the proxy gateway value.
  6. From the Mode dropdown list, select Transparent.
  7. Enable or disable encryption. By default, encryption is disabled. When encryption is enabled, traffic between FortiClient and the FortiGate is always encrypted, even if the original traffic has already been encrypted. When encryption is disabled, traffic between FortiClient and the FortiGate is not encrypted.
  8. Enable or disable User External Browser as User-agent for Saml User Authentication. When this feature is enabled, FortiClient presents a SAML authentication request to the end user in a web browser for traffic that is eligible for this rule.
  9. Click Save.