User authentication
BlackBerry UEM offers the following options to adjust the user experience for accessing BlackBerry Dynamics apps.
Fingerprint and biometric authentication
Various forms of biometric authentication are supported by the BlackBerry Dynamics SDK, including fingerprint authentication and for Android and Touch ID and Face ID for iOS. The BlackBerry UEM administrator can use a BlackBerry Dynamics profile (UEM) to enable biometric authentication. Contact your organization’s administrator to enable and configure these features.
Authentication delegation
The BlackBerry UEM administrator can configure up to three BlackBerry Dynamics apps on users’ devices to act as an authentication delegate (a primary, secondary, and tertiary delegate). When a user opens any BlackBerry Dynamics app, the device will display the login screen of the authentication delegate app. After the user logs in successfully, all of the BlackBerry Dynamics apps on the device are unlocked. The user does not need to enter a password again until the idle timeout is reached.
If you want your custom BlackBerry Dynamics app to be an authentication delegate, the UEM administrator must specify the app package ID (Android) or bundle ID (iOS) in the BlackBerry Dynamics app settings in the management console. Contact your organization’s administrator to provide this information. For instructions for specifying the package ID or bundle ID for an app, see Manage settings for a BlackBerry Dynamics app in the UEM Administration Guide.
Do not require a password
Enabled using a BlackBerry Dynamics profile, this setting removes the password login for BlackBerry Dynamics apps. Users cannot choose whether to use a password.
Do not enable authentication delegation and this setting in the same profile or policy set. This feature is supported in UEM 12.7 or later. If the setting is enabled and then disabled at a later date, users are prompted to create a password the next time they log in to a BlackBerry Dynamics app.
You can use the GDAndroid.getInstance().canAuthorizeAutonomously() or [GDiOS sharedInstance].canAuthorizeAutonomously method to check if this feature is enabled. See the GDInteraction sample app (Android) or the SecureStore sample app (iOS) for examples of this method.
Bypass the app unlock screen
Enabled in the UEM Client settings for a specific BlackBerry Dynamics app (UEM), this setting allows an app to completely bypass the password login screen.
For more information and programming guidance, see the Bypass Unlock Developer Guide.
Background Authorize
The Background Authorize feature allows a recently locked BlackBerry Dynamics app to use the principal BlackBerry Dynamics APIs (such as secure storage and secure communication) when the app is running in the background.
Background Authorize is particularly useful when a BlackBerry Dynamics app stops unexpectedly, for example, if the OS unloads it from runtime memory. An app can be started in the background in response to a push notification (for example, APNs or FCM messages for new emails), a background fetch operation, or background tasks; if Background Authorize is enabled, the BlackBerry Dynamics app can authorize autonomously, download the new data or messages, and store them in the secure container. When the user brings the app to the foreground, they can authenticate and access the new data or messages without any delay.
For more information, see Enabling Background Authorize for a BlackBerry Dynamics app.