Using an Agentry app on a shared iOS device

[former_member231132]

We have a pilot currently running at a small number of locations where people are using iPads as shared devices. This is being implemented by using an MDM (Airwatch) configuration that allows the user to log in and out of Airwatch. So when user A wants to hand the device to user B, user A simply logs out of Airwatch and then user B logs into Airwatch. This is causing a problem since when user A logs out of Airwatch the user is not automatically logged out of the applications that were being used by user A and therefore user B begins their session by being logged into the apps as user A.

I can think of three options to handle this: 1) try to programmatically detect when a user signs out of Airwatch and then automatically sign the user out of MDC or kill the app session. 2) force the user to re-authenticate each time the app opens from a minimized state. This option wouldn’t totally solve the problem but at least it prohibits user B from using user A’s account to do work in the apps. User B would still need to manually kill the app session and then log in as themself. 3) require the user to remember to log out of all applications before logging out of Airwatch (not a realistic option for this user audience).

Option 1 would be my first choice, followed by option 2.Can anyone provide any hints as to how to implement one of these options?I did find an application setting in Agentry that allows you to force a user to re-authenticate to the app after an idle timeout, but that’s based on a time limit expiring not on an Airwatch log out or the app being opened from minimized state.

Thanks very much

[mark_pe]

Tim,

Hello. From your findings: "I did find an application setting in Agentry that allows you to force a user to re-authenticate to the app after an idle timeout," <-- Typically the idle time out by default is 5 minutes. So if you think of it, if USER A logs out of Air Watch and hands over the device to USER B, then 5 minutes may have already passed then that could work, right?

But the best practice is to make the user log out of the app so that his colleagues would not have access to his/her work. So you may do this before logging out of Airwatch. With respect to Airwatch capability, hopefully other users experienced in Airwatch may comment here.

Regards,

Mark