While waiting for the patch to address potential change in the length of UDID which is hard-coded on Apple devices, I was somewhat surprised that a separate patch is also required for the Tunnel Proxy component. Given that sooner or later we will be enrolling the newly announced Apple devices, I would apply the patch now to avoid any agony from my service desk team.
While the article is pretty self-explanatory, I put this post together with screenshots to help clarify any confusion anyone may have.
Before continuing, we need to first identify the installed version of Tunnel Proxy. In my case, it’s installed on a Windows server. There are two ways to do so:
- Remote into your Tunnel Proxy server (Relay and/or Endpoint)
- Browse to C:\AirWatch\TunnelProxy\lib
- Look for file proxy-1.xx.jar. This is the version you need to update.
- You may also log onto your AirWatch / Workspace ONE UEM console.
- Navigate to GROUPS & SETTINGS -> All Settings -> System -> Enterprise Integration -> VMware Tunnel -> Configuration.
- Click TEST CONNECTION.
- Look for the version at the upper left-hand corner.
After identifying the version you need to patch, go ahead and download the latest version of the installer and the patch. You can see the links at the very top of the same patch article.
The steps to install are the same that I’ve outlined in one of my upgrade posts which you can access here. Don’t forget to give it a quick reboot after the install completes.
If upgrading with the installer is not possible, simply extract the patch from the zip file and look for the version that matches your existing install. Then, copy the file proxy-1.xx.jar file to your Tunnel Proxy server.
The remaining steps are:
- Stop the proxy service
- Backup the existing .jar file from C:\AirWatch\TunnelProxy\lib
- Replace the existing .jar file with the one extracted from the patch folder
- Start the proxy service
Regardless of which methods you use to apply the patch, be sure to perform the validation checks from both the Workspace ONE console and your mobile device to confirm all is well. The true test, of course, is to see if you experience any browser authentication issue once you enroll any of the new Apple devices.
As always, stay mobile!