Forum Discussion
I_R_101_110
Cirrus
CirrusAPM - MDM Compliance with Airwatch Fails with New F5 Access for iOS 2018 Client 3.0
The updated 3.0 version of the iOS client from the 2.1.1 version has broken the MDM query to Airwatch just as the document discussed it would with the absence of the UDID.
https://support.f5.com...
I_R_101_110Cirrus
CirrusI suppose we have a certificate common name on the iOS client device that matches the UDID assigned from Airwatch. Could I get fancy and variable assign the two missing UDID variables the value from the certificate common name?
session.client.mdm_device_unique_id - Assign value from certificate common name session.client.unique_id - Assign value from certificate common name
Could I then pass the above variables to the Airwatch system for a successful MDM compliance query?
