MobileIron officially supports Android enterprise QR code provisioning

Originally published at: https://bayton.org/2017/10/mobileiron-officially-supports-android-enterprise-qr-code-provisioning/

Overnight, MobileIron’s Provisioner app updated to version 1.2.0 and with it came the long-awaited support for QR code generation. The Mobile@Work DPC received official support for QR enrolment on the 16th of this month with version 9.5.1.0 following MobileIron Go last month, so it was only a matter of time! I’ve covered unofficial QR code support with MobileIron previously: MobileIron unofficially supports QR provisioning for Android enterprise work-managed devices, this is how I found it Manual Android enterprise work-managed QR code generation for MobileIron These articles garnered attention both within and outside of the MobileIron community, leading to the accelerated official support we see with today’s update. With that in mind, I’m obviously very interested in how it’s been implemented! As a reminder, here’s the (now supported) raw QR snippet I got working with MobileIron: { “android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME”: “com.mobileiron/com.mobileiron.receiver.MIDeviceAdmin”, “android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM”: “tlYEdUEZ3sUGJM-ySibMl0YjJXKDoUJOM1GxSSoVsrE”, “android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION”: “https://home.bayton.org/mi-android-nfc-latest.apk”, “android.app.extra.PROVISIONING_SKIP_ENCRYPTION”: false, “android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE”: { } } And below, the MobileIron Provisioner-generated QR code I decoded: { “android.app.extra.PROVISIONING_LOCALE”:“en_GB”, “android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME”:“com.mobileiron/.receiver.MIDeviceAdmin”, “android.app.extra.PROVISIONING_TIME_ZONE”:“Europe/London”, “android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION”:“https://support.mobileiron.com/android-client-nfc/mi/mi-android-nfc-latest.apk”, “android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM”:“F-Ui0YRmoacQYly_lzW8eOCHxjc9TVy6R5eQ9FtSdRk”, “android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED”:true, “android.app.extra.PROVISIONING_LOCAL_TIME”:“1508485289505”, “android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE”: { “server”:“core.bayton.org”, “user”:“jason”, “quickStart”:false, “qrCode”:true } } There are indeed a couple of differences here, the most significant being the addition of PROVISIONING_ADMIN_EXTRAS_BUNDLE which wasn’t previously supported by the Mobile@Work DPC prior to the 9.5.1.0 release; this addition makes it even easier to get enrolled as it pre-applies the server URL and username within the DPC, leaving just a password (or PIN) required in order to get started. Nice. Less significant, but very nice to support nonetheless is PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED, providing the ability to leave…