What's New in Imprivata Mobile Device Access

Imprivata Mobile Device Access 7.17 contains the following new features and technology updates.

New Features

  • Add support for lock and log out on charge. When configured with AppConfig, Imprivata MDA detects that the device is charging and will lock the device and/or log the user out of the device and log the user out of apps.

Features in Previous Releases

Previous releases of Imprivata MDA contained the following new features, enhancements, and fixes.

  • Add support for setting a default domain, so the end user does not always have to choose one from the drop-down list before authenticating to Imprivata MDA.

  • Add support for offline authentication. Offline authentication allows a user to log into Imprivata MDA even when the app cannot connect to the Imprivata server. When offline, Imprivata MDA accepts the last validated user credentials, including: proximity card, Imprivata PIN, and username + password.

  • Add support for Microsoft Entra ID domains.

  • Add support for Android 15 devices.

  • Support for external proximity badge readers.

  • Enterprise Access Management Certificate validation. Imprivata MDA 7.15 introduces new SSL configuration flags to enable trusted communication with the Enterprise Access Management (formerly OneSign) server.

  • Add Diagnostic screens for improved troubleshooting and sending logs to Imprivata Support.

  • Add support for Android 14 devices.

  • Add support for Zebra dialer.

    • Integrates with the native Zebra dialer app

    • Allows calls and notifications to work properly on Zebra devices using Imprivata MDA.

    • Calls and notifications will come through when Imprivata MDA is locked.

    • Device Language Settings and Imprivata MDA. In previous releases, Imprivata MDA would use the Imprivata OneSign mobile policy language setting to control the language of the Imprivata MDA app. Beginning with Imprivata MDA 7.14, the language is controlled by the device level localization settings, commonly set in your MDM, not by the Imprivata OneSign mobile policy.

Known Issues

The following issues may occur in Imprivata MDA 7.17:

  • On Zebra TC21 devices running Android 11, after a reboot of the device, NFC does not work and the user cannot authenticate with a proximity card. The device displays an error message: "NFC read error. Try again."

    To work around this issue, either update the device to Android 13 (or later), or put the device to sleep and wake it up with the on/off button.

  • On Android 10 devices, if the device reboots while connected to an external proximity card reader, the device incorrectly displays an 'allow Imprivata MDA to access USB keyboard' message instead of connecting automatically to the reader.

  • When the Imprivata MDA app updates, Imprivata MDA restarts after update, locking the device and requiring a user to authenticate. When the device is locked before the Imprivata MDA update, this behavior is not noticed. When the update happens during a user shift, it results with an unexpected device locking (from the user's perspective). This behavior occurs in both normal and Countdown to Lock modes.

    To work around this issue, plan your Imprivata MDA updates for a time when devices are not in use, or configure "On demand" update triggering it manually on devices.

  • On Android 12 devices enrolled in Workspace ONE with the Workspace One Launcher, after the screensaver has appeared, Imprivata MDA displays a persistent Imprivata MDA blue loading screen.

    This behavior is the same whether the allowScreensaver key is set in the AppConfig or not.

  • Imprivata MDA auto logout feature doesn't work on Samsung devices running Android 11 and later.

  • Imprivata MDA's Lock Task privileges are intermittently revoked with Workspace ONE Hub/Launcher versions 4.8 and 4.9.

    Issues have been resolved when updating to 21.06 and later.