Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 8 Next »

This guide provides instructions for configuring Infoblox Mobile Endpoint for use with Mobile Device Management (MDM) solutions. The configuration file downloaded from the Infoblox Portal contains key parameters that help manage Android, iOS, and Chrome devices within an MDM environment.

Notes

  • Proxy Mode Warning: The proxy mode feature has not been tested and may not function correctly.

  • Supported Chrome OS Versions: Chrome OS 90 and above are supported for Chrome device configuration.


Step 1: Download the MDM Configuration File from the Infoblox Portal

To configure Infoblox Mobile Endpoint for MDM solutions:

  1. Log into the Infoblox Portal.

  2. Navigate to Configure > Security > Endpoints.

  3. On the Endpoints page, click the Endpoint Groups tab.

  4. On the Endpoint Groups page, click Download MDM Configuration.

  5. On the Mobile Device Management page, download the appropriate configuration file for your device:

    • For an Android device: Click Download Android Config File.

    • For an Apple device: Click Download iOS Config File.

    • For a Chrome device: Click Download Chrome Config File. Chrome OS versions 90 and above are supported.

Step 2: Review the Configuration File Parameters

The downloaded MDM configuration file contains the following parameters:

  • joinToken: The value in the XML file, required for authentication.

  • groupName: The Infoblox Portal group to which the endpoint will be assigned. If the group does not exist, the endpoint will be added to All Infoblox Endpoints.

  • userId: A unique name that identifies a mobile device, displayed on the Endpoints page (Infoblox Portal > Configure > Security > Endpoints).

  • allowServiceControl: By default, this value is True. To disable and hide service control, toggle this value to False.

  • extensionType (iOS only): Defaults to "vpn", but can be set to "dnsproxy" to intercept DNS traffic via the DNS Proxy Provider.

  • No labels