Some folks recently reached out to me asking for help figuring out how to route NoMAD traffic over VMware Tunnel. Basically, the ask was to use Per-App Tunneling to give NoMAD the ability to obtain Kerberos Tickets and Sync AD passwords without being directly on the Enterprise network. If you’re familiar with my previous article about the macOS Catalina Kerberos SSO Plugin, you’ll know that Apple’s built-in functionality in Catalina doesn’t work well with Per-App Tunneling.
So Why Try NoMAD
If you’re not familiar with NoMAD, it’s an open-source app meant to help a user on a non-bound Mac obtain Kerberos tickets and sync their local password with a directory (Active Directory) password. It’s similar in functionality to Apple’s Enterprise Connect tool (available through Apple Professional Services). Our hope with trying NoMAD was to give someone the ability to do the same Kerberos/SSO functionality on Catalina that you can potentially do on Big Sur. The idea was not meant for long-term use and was more-so a stop-gap until devices were upgraded to Big Sur.
Setting Up NoMAD in Workspace ONE UEM
As you go through the setup, you’ll need to set up the following:
- Create and Assign a Custom Settings profile with NoMAD Preferences.
- Parse the NoMAD.pkg with Workspace ONE Admin Assistant
- Modify the metadata plist to use an installs array if you would rather check for the app versus the receipt
- Upload and create the Internal App. Add a post-install script that creates the LaunchAgent.
- Modify the Tunnel Device Traffic Rules to route traffic to your domain (AD and DNS, or *.yourdomain.com) over the per-app tunnel.
- SAVE the configuration!!
The balance of this blog post hits on the not-so-obvious configurations you’ll need to make in order to get this app deployed and working via Workspace ONE:
Custom Settings XML for NoMAD Preferences
When setting up the Custom Settings XML, you’ll need to refer to the list of preferences keys to figure out what is best for your setup. I’ve included a basic Custom Settings XML profile below. That said, a few gotchas you may want to consider:
- KerberosRealm needs to be specified in ALL CAPS.
- Determine if you want to supply the LDAPServerList to specify a list of DC’s. Without including this, NoMAD attempts to find DC’s via DNS.
<dict> <key>PayloadDisplayName</key> <string>NoMAD Preferences</string> <key>PayloadIdentifier</key> <string>com.trusourcelabs.NoMAD.8B3D35B1-61AD-4017-97BA-A383A61B90FA</string> <key>PayloadOrganization</key> <string>VMware</string> <key>PayloadType</key> <string>com.trusourcelabs.NoMAD</string> <key>PayloadUUID</key> <string>8B3D35B1-61AD-4017-97BA-A383A61B90FA</string> <key>PayloadVersion</key> <integer>1</integer> <key>ADDomain</key> <string>YOURDOMAIN.COM</string> <key>KerberosRealm</key> <string>YOURDOMAIN.COM</string> <key>RenewTickets</key> <string>1</string> <key>SecondsToRenew</key> <string>7200</string> <key>ShowHome</key> <string>0</string> <key>Template</key> <string>User Auth</string> <key>UseKeychain</key> <true/> <key>Verbose</key> <true/> <key>DontShowWelcome</key> <true/> <key>HideAbout</key> <true/> <key>HidePrefs</key> <true/> <key>HideGetSoftware</key> <true/> <key>LDAPServerList</key> <string>dc1.yourdomain.com,dc2.yourdomain.com</string> <key>LocalPasswordSync</key> <true/> <key>RenewTickets</key> <true/> </dict>
Per-App Tunnel Device Traffic Rules
In the Device Traffic Rules, you’ll first need to set up the macOS App Definition. The critical info you’ll need is this:
- Platform: macOS
- Friendly Name: NoMAD
- Package ID:
- Designated Requirement:
anchor apple generic and identifier "com.trusourcelabs.NoMAD" and (certificate leaf[field.1.2.840.113622.214.171.124.9] /* exists */ or certificate 1[field.1.2.840.1136126.96.36.199.6] /* exists */ and certificate leaf[field.1.2.840.1136188.8.131.52.13] /* exists */ and certificate leaf[subject.OU] = AAPZK3CB24)
With the App definition in place, you can then add your device traffic rule. Set Safari and NoMAD to
Tunnel to the list of DCs you’ve placed in your serverlist (or you can simply with a wildcard) –
*.domain.com. I add Safari so I can do some testing but it is optional.
PostInstall Script for NoMAD Internal App
When setting up NoMAD as an internal application for macOS, you’ll want to add the following as a post install script:
#!/bin/sh /usr/local/bin/hubcli profiles --install 1041 #Where the number is the profile ID for the NoMAD Custom Settings /usr/bin/touch /Library/LaunchAgents/com.trusourcelabs.NoMAD.plist /bin/cat > /Library/LaunchAgents/com.trusourcelabs.NoMAD.plist <<- EOM <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>KeepAlive</key> <true/> <key>Label</key> <string>com.trusourcelabs.NoMAD</string> <key>LimitLoadToSessionType</key> <array> <string>Aqua</string> </array> <key>ProgramArguments</key> <array> <string>/Applications/NoMAD.app/Contents/MacOS/NoMAD</string> </array> <key>RunAtLoad</key> <true/> </dict> </plist> EOM
It’s important to note that much of what I’ve done in this post is applicable to many other Apps that you’d commonly deploy with Workspace ONE UEM. That said, I expect that some of this procedure will change over time as FreeStyle gains additional functionality.