Configuring Bloxone Endpoint for iOS in Jamf

My company is looking to start managing iPads, and with that, we’ve got to make sure the security of the devices is also taken care of.

Being Infoblox customers, we are utilizing their BloxOne Mobile Endpoint solution. Unfortunately there isn’t really anything in the way of documentation on how to manage the configuration of the application via Jamf, so I had to hunt down a solution.

Head to the Mobile Device Apps section in Jamf and go to the BloxOne EP app > App Configuration, then enter the following:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10

<dict>
 <key>allowServiceControl</key>
 <true></true>
 <key>customerId</key>
 <string>YOUR CUSTOMER ID</string>
 <key>groupName</key>
 <string>YOUR GROUP NAME</string>
 <key>userId</key>
 <string>YOUR USER ID</string>
</dict>

This information is provided to you by Infoblox via an MDM config file that they give you; however, it’s in the wrong format, and it took me a while to figure out exactly what Jamf wanted from the data I was given.

Here are the contents of the given file, aptly named, ios-config.xml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

<?xml version="1.0" encoding="UTF-8"?>
  <managedAppConfiguration>
      <dict>
          <boolean keyName="allowServiceControl">
              <defaultValue>
                  <value>true</value>
              </defaultValue>
          </boolean>
          <string keyName="customerId">
              <defaultValue>
                  <value>YOUR CUSTOMER ID</value>
              </defaultValue>
          </string>
          <string keyName="groupName">
              <defaultValue>
                  <value>YOUR GROUP NAME</value>
              </defaultValue>
          </string>
          <string keyName="userId">
              <defaultValue>
                  <value>YOUR USER ID</value>
              </defaultValue>
          </string>
      </dict>
  </managedAppConfiguration>

As you can see, there’s quite a bit of chaff in there, at least as it pertains to the Jamf configuration. It also didn’t help much that Infoblox has “Enrollment of BloxOne Mobile Device Management App” articles for every just about every MDM except for Jamf.

Although I’d originally thought that using an XML format would be fine, Jamf wants the configuration in more of a plist format. Honestly, I’m fine with this. In my opinion it’s a much cleaner read as well.
With this you can reasonably apply the logic to any other iOS app configurations that you run into, and convert any XML given into plist.