Check Out Devices via Imprivata Locker

NOTE:

Applies to iOS devices.

Supported in the MAM 8.0 User Acceptance Test (UAT) environment.

Download a PDF of this guide.

Over the air (OTA) checkout ("Grab and Go") enables users to check out iPhone and iPad devices without requiring Launchpad computers or Smart Hub charging hardware. This supports deployments that do not require physical Check Out infrastructure.

With traditional Launchpad-based Check Out ("Tap and Go"), users tap their badge on a card reader attached to a Smart Hub. With Grab and Go, users authenticate directly on the iOS device itself via badge tap (NFC), face recognition, QR code scan, or username/password entry from any location.

  • All checkout events are logged in the Activity tab with the authentication method used (badge, face, QR code, or username/password) recorded for audit purposes.

  • This feature can be used alongside standard Launchpad-based Check Out workflows and devices can still be provisioned by a Launchpad.

  • Grab and Go devices must be initially provisioned and checked in to a Launchpad.

  • Devices can be used with or without device level passcodes.

Grab and Go lockscreen on an iPad and an iPhone

Assumptions

This guide assumes that your MAM organization is already configured in the following manner:

Requirements

The Grab and Go feature requires the following:

  • MAM 8.0 or later.

  • Imprivata Locker iOS 5.0 and later.

  • iOS devices running a supported version of iOS/iPadOS.

  • Requires device internet connectivity to the MAM server.

  • Face recognition:

  • NFC badges:

    • iPhone 15 and later with NFC reader mode.

    • Badges must be ISO/IEC 14443 Type A compliant by using the 13.56 MHz MIFARE NFC Frequency. If your current badges do not support this frequency, there are two options available:

      • Replace existing badges with new badges that support dual frequency (both 125 kHz and 13.56 MHz).

      • Attach stickers to the badges to allow for 13.56 MHz frequency to be read. When adding a sticker that supports the 13.56 MHz frequency, configure the EAM user policy to allow more than one badge per user. For more information, see Integrate with Imprivata Enterprise Access Management.

  • QR codes:

    • QR codes must be generated externally. This task is beyond the scope of this documentation.

      QR codes may be generated from badge IDs exported from Imprivata Enterprise Access Management or can be generated in GUID standard format and enrolled in Locker.

      Example

      Export badge 12345 from EAM and generate a QR code for badge:12345.

      Alternately, generate a GUID such as fc1cb445-7d4a-4253-817c-1b15f32ba67e and then generate a QR code for badge:fc1cb445-7d4a-4253-817c-1b15f32ba67e.

    • The user must grant access to the device's front facing camera.

Supported Authentication Methods

The following table illustrates the supported authentication methods:

Authentication Method Notes
Face recognition

Users check out a device using their face, but must follow up by using a second factor to authenticate.

  • Users can enroll their face during device checkout.

  • When Imprivata PIN is used as a second factor, the user can enroll their Imprivata PIN during device checkout.

NFC badge tap

Users check out a device by tapping their badge on the device.

Users can enroll their badge during device checkout, if it is enabled in Admin > Check Out.

Username and password

Users check out a device using their username and password.

QR code

Users scan their QR code as a first factor to check out a device, but must follow up by using a second factor to authenticate.

Supported Badge Types

Locker supports tapping an NFC enabled badge to check out on compatible iPhone models with compatible badge types.

Badge Type
ISO 14443 A
NTAG 213/215/216

MIFARE DESFire EV1/EV2/EV3 (UID read only)

Interactions with Other MAM Features

The Grab and Go feature interacts favorably with other MAM features:

  • Devices checked out via Locker are displayed in the Device Home Dashboard.

  • Passcode-locked devices. Department Managers can clear the passcode from an abandoned device. Clearing the passcode does not sign the user out of apps.

    With the device in their possession, the Department Manager must then open Locker and check in the device or return it to a Launchpad.

  • App sign-in using Enterprise Password AutoFill or OpenID Connect (OIDC).

  • Personalized Lock Screen using Live Activities.

  • Checking the device out starts the overdue timer; check in clears an Overdue status.

  • Devices marked as out of service (using the Out of Service device attribute) cannot be checked out. An administrator must change the device's status.

Limitations

  • iPads do not contain NFC reader hardware, but can be used with QR Code or Face to check out.

  • Over the air (OTA) Workflows remove all other actions when the Check Out action is added.

  • You cannot mix an OTA Check Out action with non-OTA actions in the same automation chain.

  • Grab and Go does not support the ability to force quit apps on device check in.

  • Check In via Locker must be initiated manually by the user tapping the Logout button in the Locker app. It cannot be checked in over the air remotely from the MAM server.

Configure Check Out and Check In