Configuring GlobalProtect iOS App with XenMobile MDM

[jwolach]

Does anyone have a write-up on how to configure the new GlobalProtect iOS App with Citrix's XenMobile MDM or any MDM?

Thanks,

Jeff

[jmenon · Accepted solution]

You could use Custom SSL to configure GlobalProtect app , till MDM vendors update their software.

Identifier is com.paloaltonetworks.GlobalProtect.vpnplugin

Attached screen shot from IPCU for an example

[jwolach]

Hi Jmenon,

I did what you recommended by creating a Custom SSL VPN Policy in my MDM and then deployed it with the GP iOS app.  It did not populate the GP iOS app settings like I thought it would and when I opened the GP iOS app on the iDevice it then created a separate VPN configuration in the settings.

Not sure i

[jmenon]

double check you identifier is correct

<key>VPNSubType</key>

  <string>com.paloaltonetworks.GlobalProtect.vpnplugin</string>

  <key>VPNType</key>

  <string>VPN</string>

Aslo from iOS settings make the one deployed from MDM the default/selected and then launch the GlobalProtect app to see if the profile gets loaded.

[jwolach]

Still doesn't populate the GP app information.

Here's my XenMobile VPN Policy Configuration.  It doesn't allow me to put in the second Key parameter for VPNType and String for VPN.

[jwolach]

After looking over your parameters, I changed mine but, still doen't populate.

[jmenon]

You don't need to configure custom parameters. You may want to try with IPCU iPhone Configuration Utility 3.5 for Mac OS X and/or also contact XenMobile support.

We will also sync up with XenMobile to figure where the fallout may be happening.

[jwolach]

Jmenon,

Finally, got it to work.  You're not going to believe it.  If you take a look at your very first reply to my original question, you will notice that the work paloaltonetworks is misspelled and stupid me, I just cut-n-pasted the identifier from that reply. LOL!!  Once, I corrected the misspell, everything populated just fine.

Thanks for you help and patience.

Kind regards,

Jeff

[jmenon]

Glad that it worked. I also edited my original reply to correct the typo for the benefit of others. Thanks for pointing it out.