Hello everybody,
regarding ZTNA, we found a bug after yesterday Forticlient EMS 7.2.5 upgrade.
This is happening only on macOS devices.
We have a ZTNA destination profile:
On Windows device, rule are correctly retrivied. But, on macOS, I can see no destination (I have all the tags I need):
Debbuging this problem, I was looking at the Forticlient ztna.logs, and I found (I removed some rules for simplification):
2024-10-11T16:24:28.238 TZ=+0200 info ztna mergeCfg:{"enabled":1,"rules":[{"name":"EMS","mode":"transparent","enabled":0,"destination":"10.1.0.217:3389","gateway":"ztna.ntditalia.com:13389","encryption":1,"local_port":"7788","type":"private"},{"name":"VMAgostini","mode":"transparent","enabled":0,"destination":"10.1.0.215:3389","gateway":"ztna.ntditalia.com:13389","encryption":1,"local_port":"7788","type":"private"}],"portals":null,"gateways":null,"notify_on_error":1,"portals_enabled":1,"gateways_enabled":1}
2024-10-11T16:24:57.148 TZ=+0200 info ztna sync portal select portal err:errPortalNotExisted
If we look at this logs, the rules are found, but are not enable (enable is 0).
In fact, if I look at the ztnaconfig.json:
{"enabled":1,"rules":[]}
if I manually add my desinations inside the rules array, I can reach them correctly. So, the problem is that forticlient can't receive correctly the rules (am I wrong?). The only error I can see is info ztna sync portal select portal err:errPortalNotExisted.
What does it mean? I can't find anything regarding this error. This only happens for macOS system.
Thank you!
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
I solved the problem. The solution was to create manually the XML ZTNA configuration. I had to shift down the "gateways" tag, in order to be correctly recognized by the Forticlient on macOS.
Hi There,
I hope your issue is resolved by now.
Thanks,
No, it's not.
I investigated the problem and I think it is simply a bug.
Looking at the XML configuration of the ZTNA:
As you can see, the problem is the problem is that whatever the configuration, the destinations arrive with the enable parameter set to 0.
I solved the problem. The solution was to create manually the XML ZTNA configuration. I had to shift down the "gateways" tag, in order to be correctly recognized by the Forticlient on macOS.
Hello! We're having the exact same issue...but I don't quite understand your fix. Could you give me a little more info/detail on what you meant by "shift down the 'gateways' tag"? Thanks!!!
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1696 | |
1091 | |
752 | |
446 | |
228 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.