Hosting side is already using Edge Router (bind configured on ER, not C-SDK)
Dial side is using C-SDK - this is where we see the connect/disconnect issue
We are still getting the same behavior using the Mac OS SDK. I need to do more test because with the new Windows Client (2.8.4.0) it does not seem to fail on the dial side with the ER as bind.
This weekend I will test with ER/T or ziti tunnel on the dial side (replacing C-SDK client) to isolate if it's a C-SDK dial issue.
failed to connect, reason=failed to create service token from JWT: api session id (c6c639ea-efa8-4f6d-87d0-014b83d89c62) does not match service session api session id (671235b4-025a-4ef7-a957-2f580c240e88)
I just have a follow-up regarding the Windows client — the issue is a bit different. It works fine initially with OIDC (Entra ID). At first, I can connect to all services without any issues. But after a while, the events mentioned above start to appear, and I’m unable to connect to any services until I disconnect and reconnect the client.
Hi @msbusk, with respect to windows, would you be willing to give the ZDEW "beta" stream a try? It'll help us to know if the issue is (or is not) fixed with the latest client. You can go to Main Menu -> Advanced Settings -> Configure Automatic Upgrades change the url to https://get.openziti.io/zdew/beta.json and click "set update URL". You can then "check for Updates Now" and then request an update.
That will get you the latest ZDEW (2.9.0.0) to try with.
Thanks for the suggestion about the beta version — I’m happy to take it and test with that. I’ve just installed it on a test machine and will go through it to see how it behaves.
I noticed that the following issues were fixed in the stable version on GitHub:
fixed an issue that caused service terminators to accumulate when hosted service configurations changed
fixed a potential when hosted services become unavailable
fixes API session refresh failure when connected with edge router versions 1.6-1.8
That’s actually why I chose the stable version over the beta, but those fixes may of course also be included in the beta version.
With Pre-release 5 and the latest beta clients for Windows, everything seems to be working. So it looks like it’s only the macOS clients that are having issues right now.
The beta client for Windows resolves the issue completely. However, the problem is still present on the macOS client.
Is there any information I can provide that would help you investigate the issue further, or do you already have what you need?
We're being a bit cautious with releases lately. The Windows tunneler is able to have multiple release streams but it's not so cut and dry for the MacOS client. If the windows beta fixes it, the upcoming MacOS release should as well, you'll just have to wait for that MacOS release to come out, unfortunately.
That sounds good – thank you for the information.
We’re looking forward to the final release of ZITI 1.8 as well as the new client versions in general in GA/Stable.
I don’t expect to release the macOS client this week, but the fixes that will help you are available in a test flight build of Ziti Desktop Edge for macOS. If you DM me the email address of the Apple ID that you’re running ZDEm with I can send you a test flight invitation.