Fortigate ZTNA Tag added in policy, SSLVPN cannot access local LAN

[lamkayiu]

Dear All

I just purchased EMS last week and setup finished, everything seems fine at EMS server. I want to use EMS ZTNA to control SSLVPN user who only match zero trust tag can access lan server. When I added the tag make my SSLVPN cannot access my Local LAN, removed it everything is fine. Any step I am missing or incorrect setup ?

Resolved Address can see my vpn ip

View matched endpoint can see my laptop, but it still show 0  when I move the mouse on it.

Firewall policy added tag - cannot access lan server

Removed tag everything fine

Connection is ok

 I can view all zero trust tag at EMS portal

Creat new tag "Test" and fortigate also can show up

[abc]

Strange one on my end. I disabled all the firewall polices that had ZTNA tags, reenabled them and they are working!!

[Debbie_FTNT]

Hey abc,

Yes I am - this is an offshoot of a lab I set up for ZTNA, and I just needed very simple tags I could match or not, so the tags I have set are just based off IP range.

[Ronny]

We also have the problem in a production environment. The tags for SSL VPN and IPSEC VPN are simply not synchronized. A side effect is that the Fortigate is also regularly out of sync.

[KK_PRL]

---

@Debbie_FTNT wrote:

...

I do have to wait a minute or two for EMS to have the updated client IP after VPN is established; then my VPN client is able to access resources through a policy with tags.

---

Hello,

I have made same setup and it works, but the waiting till 2minutes, when tag will assigned is annoying. Is it possible to shorted waiting time? We use Forticlient and EMS 7.2.3

[martin28]

Hello,

It is a known bug that forticlient cannot get VPN IP address correctly, we will have to wait for another release to fix this bug.