Forum Discussion

I_R_101_110's avatar
I_R_101_110
Icon for Cirrus rankCirrus
Jun 29, 2018

APM - 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/content/kb/en-us/products/big-ip_apm/manuals/related/apm-f5access-ios-3-0-0/_jcr_content/pdfAttach/download/file.res/apm_f5_access_ios_3-0-0.pdf

 

Is there a work around in place to force compliance even in the absence of a UDID in the 3.0 version or will it be resolved in firmware or elsewhere before the 2.1.1 version is deprecated?

 

application delivery
BIG-IP Access Policy Manager (APM)
  • I_R_101_110's avatar
    I_R_101_110
    Icon for Cirrus rankCirrus
    Jun 29, 2018

    I 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?