Forum Discussion
AltostratusAPM integration with MobileIron not retrieving variables
I'm attempting to query MobileIron from APM to determine if a device is compliant. I'm using the instructions posted here but when I attempt to logon from one of the MI controlled devices it fails and I see the following entry in the session logs:
.session.mobileiron.connection_status 7 invalid
Yet when I run "curl -G --user : https://miserver.domain.com/api/v1/dm/devices/mac/devicemacaddress" from the Big-IP it is able to retrieve all of the device information.
Is there a way to identify what, exactly, isn't working between the APM and MobileIron VSP server?
This issue was fixed by downloading an updated version of the iApp at:
https://github.com/MattDierick/MobileIron-iApp
The iRule needs to be tweaked a bit, or at least it did for our environment. The iRule looks for a url using format of https://miserver.domain.com/rest/api/v2/devices. For my environment at least the /rest is not in the url query field. I removed that so it points to https://miserver.domain.com/api/v2/devices. After making that change it worked like a charm.
4 Replies
Arnaud_LemaireEmployee
Hello, connection_status seams to be invalid either if device is not compliant or if you have a connection error to the cloud. Could you check apm logs to see if anything appears ?
- Arnaud_Lemaire
Hello, connection_status seams to be invalid either if device is not compliant or if you have a connection error to the cloud. Could you check apm logs to see if anything appears ?
- Arnaud_Lemaire
Hello, connection_status seams to be invalid either if device is not compliant or if you have a connection error to the cloud. Could you check apm logs to see if anything appears ?
Jonathan_WingfiThis issue was fixed by downloading an updated version of the iApp at:
https://github.com/MattDierick/MobileIron-iApp
The iRule needs to be tweaked a bit, or at least it did for our environment. The iRule looks for a url using format of https://miserver.domain.com/rest/api/v2/devices. For my environment at least the /rest is not in the url query field. I removed that so it points to https://miserver.domain.com/api/v2/devices. After making that change it worked like a charm.
