APM call Airwatch API To check device compliance

We use a sideband call to AW API for that. Just put the serial number attribute in the certificate and then query the API for that device. We used an example sideband iRule that we received from F5 and adopted this to our requirements.

Hello, Thanks a lot for your comment. If it's possible, because I am mewbie on F5, could you share the model of sideband rule you used ? Thanks a lot for your help.

Hello,

 

If you upgrade to v12.0.0, you will be able to use the built in MDM integration with Airwatch which is much more convenient than using an irule with sideband connections.

 

If you really want to use sideband, you can take inspiration with the following article for mobileIron : https://devcentral.f5.com/tech-tips/articles/integrating-apm-with-mobileiron-mdm-ndash-part-1

 

Hi, I am trying to do this exact use case with a device certificate and serial number in the certificate, but I cannot find which variable to use to query the AW API. Does anyone have any insight into which variable to use for this?

 

I have been referred to this link but it states it is using the UDID and not the serial number.

 

https://support.f5.com/content/kb/en-us/products/big-ip_apm/manuals/related/apm-edgeclientios-2-0-8/_jcr_content/pdfAttach/download_0/file.res/edge-client-ios-apm-2-0-8.pdf & this link https://support.f5.com/csp/article/K12749

 

session.client.unique_id = Contains the UDID* of the iOS device

 

Update: Okay, here is what I did to figure out what the F5 edge client is sending in this variable, I setup another VS configured for On-Demand VPN, using this article https://devcentral.f5.com/s/articles/apm-cookbook-on-demand-vpn-for-ios-devices. Installed the F5 Edge Client on my mobile, connected to my internal wireless and initiated a vpn session to the VS.

 

Results: The session.client.unique_id variable was indeed populated my devices UDID.