Mobile Authenticator Studio—Version 5.1.0 (April 2024)

The following is an overview of new features introduced in Mobile Authenticator Studio 5.x. For more details about these features and how to integrate them, see the Mobile Authenticator Studio product documentation.

Mobile Authenticator Studio displays a one-time password (OTP) for a single or multiple user accounts on the device's Home screen. The user can copy the generated OTP for their user account to the clipboard and paste it into another app.

You can configure in-app help for your users in the Mobile Authenticator Studio app. This help can then be accessed by tapping the three dots and Help in the app menu.

The transaction data signing functionality in Mobile Authenticator Studio 4.x has been extended. The Manual Transaction Data Signing feature gives users the ability to approve multiple pending transactions for multiple user accounts on a specific device.

The Push and Sign feature enables users to approve a transaction after being notified by a push notification. To send the notification to Mobile Authenticator Studio, the OneSpan Mobile Security Suite Notification SDK Server can be used. For more information, refer to the Notification SDK Integration Guide.

The Scan and sign feature enables the user to sign transactions using a Cronto image. This feature is designed to use only the Secure Channel Message function to sign single transactions for a given user account.

The App-to-App signing feature gives users with activated accounts the ability to approve a pending request from a third-party application or webpage with their mobile device.

For troubleshooting purposes, you can generate reports for unexpected terminations of Mobile Authenticator Studio apps on various mobile devices. These reports are created and sent automatically and do not require any configuration. Any time the user's app terminates unexpectedly, a report will be sent automatically from the user's app.

The data collected and processed either by Mobile Authenticator Studio or Sentry does not contain any personal data of the user!

To meet accessibility standards, the Mobile Authenticator Studio app now supports platform features such as TalkBack (Android) and VoiceOver (iOS). With this, Mobile Authenticator Studio enables its users to navigate through the screens with gestures and voice control.

The overall goal with Mobile Authenticator Studio version 5.1 and following versions is to provide a better user experience with a modernized user interface and greater app stability. Also, best practices for Android and iOS have been implemented.

With this, a number of features from Mobile Authenticator Studio 4.x have either become obsolete as of version 5.1 and have been removed or replaced with more secure variations, or will be implemented in future versions. This applies to the following:

• Activation, authentication, data validation

  • Online activation

    This feature will be available again in future versions, with an enhanced and more secure implementation of the Digipass Software Advanced Provisioning Protocol (DSAPP) and greater flexibility.

  • Online Post-activation

    This feature is no longer supported in version 5.1. Mobile Authenticator Studio 5.1 offers offline post activation to confirm that the activation has been successful.

  • Manual signature and challenge input

    This feature is no longer supported in version 5.1.

  • Send generated OTP to a configured URL for automatic validation

    This feature is no longer supported in

  • Authentication based on score criteria

    This feature is no longer supported in version 5.1.

  • Root detection

    This feature is no longer supported in version 5.1.

  • SSL pinning

    SSL pinning verifies the public keys of servers before allowing communication. This will be included in a future release.

  • Time synchronization

    This feature is no longer supported in version 5.1.

• App settings and features

  • Customization

    In Mobile Authenticator Studio version 4.x, the entire app can be customized, with countless parameters to observe. Also, each menu and label can have customized colors.

    In version 5.1, best operating system practices were applied and only a primary color must be chosen for improved app screen harmonization. This color is applied to several app components such as buttons and icons. This facilitates harmonized customization of the app. For more information, see Integrate app customization.

    In a future release, a Mobile Authenticator Studio app builder tool will be available to facilitate customizing apps.

  • Action launch at startup/Auto-launch

    In version 4.x it is possible to integrate the automatic launch of actions when starting the Mobile Authenticator Studio app. In version 5.1, the OTP is automatically displayed, if the app customization specifies this as the only available action. If several actions are enabled, the app displays a list of possible actions by default.

  • Free language choice

    Mobile Authenticator Studio 5.1 is available in five default languages. Further languages and the possibility to define which languages are supported will be implemented in a future release.

  • Protection of the Mobile Authenticator Studio app

    In version 4.x, protecting the Mobile Authenticator Studio app with password and/or biometry is optional. As of version 5.1, a 6-digit PIN code to protect the app is foreseen, whereas biometric protection remains optional.

  • Check update

    This feature is no longer supported in version 5.1.

  • Static vector versions

    On iOS, Mobile Authenticator Studio version 5.1 only supports static vectors V8 or later. Support for earlier versions will be added in a future release.

  • Offline help

    Version 5.1 offers online help in the form of a link to a configurable external help page.

  • Web browsing

    Version 5.1 no longer provides a button in the Home screen to open external pages in a browser.

  • End user license agreement (EULA)

    In version 5.1, the EULA is no longer displayed at app start.

When your institution upgrades from Mobile Authenticator Studio 4.x to 5.1, your customers will encounter some prompts to migrate from the old process to the new one. The migration process is triggered each time when a non-migrated account is used for an operation.

If no user account is activated for the Mobile Authenticator Studio app, no migration is needed.