Configure Zebra SDK Based App Logout

Configure Imprivata MDA to allow it to use Zebra based logout instead of Accessibility based logout on Zebra devices.

Imprivata MDA logout methods are now extended with Zebra SDK based Clear data, Clear cache and Force stop.

In some cases, Accessibility based logout is not possible as it relies on the Settings app which can be blocked for opening – Zebra SDK based logout can be a good replacement for Accessibility logout in this instance.

With the Zebra SDK logout enabled, Imprivata MDA will attempt the logout two times using the Zebra SDK and two times using Accessibility.

Prerequisites

Take note of the following prerequisites:

  • Requires Zebra devices.

  • Requires Imprivata MDA 7.13.3 or later.

Limitations

Consider the following limitations:

  • Zebra based Force stop may not work on some devices or MDM configurations.

    BEST PRACTICE:

    Imprivata strongly recommends that you test Zebra SDK based logout on a specific device deployment.

    Most likely, if it works on one device, it will work on similar devices and enrollments. However, different Android versions may have different behavior, even on the same device model.

  • The Zebra SDK (not the Imprivata MDA implementation of it) has some portability limitations because some Zebra based logout methods can be unavailable on older operating systems like Android 8.1, or when Zebra devices are enrolled in an MDM system. Different behaviors can be seen on the same model devices but with different Android versions.

    BEST PRACTICE:

    For this reason, Imprivata strongly recommends that customers test Zebra based SDK logout functionality on all device models and Android versions.

    When a new group of device models and Android versions are added to the customer's device fleet, Imprivata recommends that you test several devices to validate that Zebra SDK logout behaves as expected.

Configure the MDM AppConfig

The logout actions are defined in the MDM AppConfig. For additional information on configuring apps via AppConfig, see your MDM documentation.

See the Imprivata MDA AppConfig Reference for supported MDM AppConfig keys.

Enable All SDK Based Logout Methods

To enable all SDK based logout methods, add the following key:

  • ConfigFlags - Allows logout actions in Imprivata MDA.

    The AppConfig Configuration Key field is "ConfigFlags".

    • The AppConfig Value Type for this feature is "String".

    • The AppConfig Value is deviceSdkLogout.

    NOTE:

    Using the deviceSdkLogout value enables all SDK based logout methods, and is equal to specifying all three individual values: deviceSdkClearData, deviceSdkClearCache, and deviceSdkForceStop.

Enable Clear Data

To enable clear data based on the SDK, add the following key:

  • The AppConfig Configuration Key field is "ConfigFlags".

    • The AppConfig Value Type for this feature is "String".

    • The AppConfig Value is deviceSdkClearData.

Enable Clear Cache

To enable clear cache based on the SDK, add the following key:

  • The AppConfig Configuration Key field is "ConfigFlags".

    • The AppConfig Value Type for this feature is "String".

    • The AppConfig Value is deviceSdkClearCache.

Enable Force Stop

To enable force stop based on the SDK, add the following key:

  • The AppConfig Configuration Key field is "ConfigFlags".

    • The AppConfig Value Type for this feature is "String".

    • The AppConfig Value is deviceSdkForceStop.