Mobile Authenticator Studio—Version 5.2.0 (November 2024)

Mobile Authenticator Studio now protects encryption keys with biometric user authentication. The PIN is stored in encrypted form with a key that is bound to biometry, and the storage containing the PIN is created with biometric protection enabled. The underlying API only returns the encryption key to the application if the user successfully authenticates with biometry. This makes it impossible to retrieve the PIN value without biometry. According to the configured authentication method, the user is now additionally prompted either for biometric authentication or to enter a PIN in the following cases:

• Activating an account offline in single-device licensing mode

• Activating an authenticator instance in multi-device licensing mode

• Changing the PIN

• Migrating the PIN

• Enabling biometric authentication

You can now configure the Mobile Authenticator Studio app to also provide offline help via the app menu. If the app is configured to provide offline help, the user can access the helpSettings screen by taping the three dots, and selecting Help. The app will then display the help content.

Mobile Authenticator Studio now offers enhanced multi-language support. You can add languages and/or remove any of the default languages except English as well as customize the default text strings.

For the language and text customizations, OneSpan provides a CSV file. You update this file as required and return the updated CSV file to OneSpan. Your customizations will be implemented accordingly in the Mobile Authenticator Studio app.

English is mandatory as in-app language and cannot be removed. If any text string values are missing, Mobile Authenticator Studio will use the corresponding English texts.

For more information about the integration of this feature, see Integrate app customization.

To facilitate the user's orientation when managing accounts, sequence numbers have been added to the Manage account, Delete account, and Rename account screens.

Mobile Authenticator Studio 5.2.0 supports supports SSL pinning. This is a security technique that ensures a client communicates only with a specified server by validating its public key, thereby preventing Man-in-the-middle attacks.

To enable SSL pinning, you need to embed the public key of your server in your mobile application. Upon connection, the client compares the server's public key against the embedded one. If they match the connection is established; if they do not match the connection is terminated.

You can export a PEM-encoded certificate from a keystore using keytool with this command:

keytool -export -alias MyCertificateAlias -keystore MyKeyStore.keystore -rfc -file MyPEMCertificate.pem

You can export a PEM-encoded certificate using OpenSSL with this command:

openssl x509 -pubkey -noout -in MyPEMCertificate.pem