Main differences between Mobile Authenticator Studio versions 4.x and 5.x

The overall goal with Mobile Authenticator Studio as of version 5.1 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 in Mobile Authenticator Studio 5.x 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. Mobile Authenticator Studio 5.x offers offline post activation to confirm that the activation has been successful.

  • Manual signature and challenge input

    This feature is no longer supported in Mobile Authenticator Studio 5.x.

  • 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 Mobile Authenticator Studio 5.x.

  • Root detection

    This feature is no longer supported in Mobile Authenticator Studio 5.x.

  • Time synchronization

    This feature is no longer supported in Mobile Authenticator Studio 5.x.

• 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 Mobile Authenticator Studio version 5.x, 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. As of 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.x 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 Mobile Authenticator Studio 4.x, protecting the Mobile Authenticator Studio app with password and/or biometry is optional. In Mobile Authenticator Studio 5.x, 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 Mobile Authenticator Studio 5.x.

  • Static vector versions

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

  • Web browsing

    Mobile Authenticator Studio 5.x no longer provides a button in the home screen to open external pages in a browser.

  • End user license agreement (EULA)

    In Mobile Authenticator Studio 5.x, the EULA is no longer displayed at app start.