Subnet as ZTNA destination

[AEK]

Hi ZTNA admins

Can a subnet be used as ZTNA destination? E.g.: "10.1.1.0/24:443".

Actually EMS and FortiGate accept it as configuration without error, and we can see it propagated on the client as a ZTNA destination, however when I try access a host (e.g.: 10.1.1.20:443) from the client it seems not working.

So am I missing something or is it just not supported?

[amrit]

I don’t think ZTNA subnet is supported. Only host FQDN or IPs is  a valid parameter. ZTNA destinations are mapped to a Real server IP in the backend using ZTNA access proxy. It is not possible to use subnets in the ZTNA servers. https://docs.fortinet.com/document/forticlient/7.4.0/administration-guide/403758/ztna-destination

[AEK]

Thanks for your response, Amritpal.

I understand and I find it logical.

In that case I think the user should be warned with an error message when he enters a subnet as destination.

[Anil_Solakoglu · Accepted solution]

Hi AEK, 

Currently, ZTNA destinations for support options Select IP, IP Range, FQDN, Wildcard FQDN, or CIDR are supported via EMS version 7.2.5.

However, it will be only supported via Forticlient 7.4.1 which is currently not released. 

I would suggest waiting for the GA build to check the persistence of the issue. 

https://docs.fortinet.com/document/forticlient/7.2.5/ems-administration-guide/543857/ztna-destinatio...

[AEK]

Hi Anil

Thanks for your response.

So we'll wait for 7.4.1.