Overview of Mobile Authenticator Studio features
- 23 Oct 2024
- 2 Minutes to read
- DarkLight
Overview of Mobile Authenticator Studio features
- Updated on 23 Oct 2024
- 2 Minutes to read
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Mobile Authenticator Studio features provides an overview of the Mobile Authenticator Studio features.
Features | Description |
|---|---|
One-time password | The generation of a one-time password (OTP) can be time-based, event-based, or time- and event-based. OTPs can be generated in Response-Only or Challenge/Response mode. |
E-signature | Digital signature generation can be time-based, event-based, or time- and event-based. |
Password protection | All sensitive features are protected from unauthorized access by a password. |
Biometric protection | On mobile devices with a biometric sensor (Touch ID or Face ID on iOS, fingerprint sensor on Android), users can protect their activated authenticator using biometric protection. |
Secure data storage | Data may be encrypted with a local password in addition to the default device-dependent encryption for secure storage on the device and protection from unauthorized access. |
Secure Channel (multi-device licensing) | One-way channel to encrypt the communication between the server and the authenticator account with a randomly generated symmetric key, the payload key. |
Transaction Data Signing | Transaction data that is stored on a server can be signed. |
Push Notification (multi-device licensing) | The Mobile Authenticator Studio app can receive push notifications that inform the user about pending transactions. This feature is available only for Android and iOS. |
Offline activation | The app can be activated in offline mode based on data entered by the user. |
Runtime Application Self-Protection | The Mobile Authenticator Studio app can be protected against attacks that target the running app. This feature is available only for Android and iOS. |
Time synchronization | The time reference used by the app can be synchronized with the server time to ensure maximum convenience for user while traveling. |
End user license agreement | The Mobile Authenticator Studio app can be configured to display a EULA at startup. |
Authenticator information | The Mobile Authenticator Studio app can be configured to display authenticator information, which may be useful for troubleshooting. |
Auto-launch | Users can launch a Mobile Authenticator Studio app and execute a defined action by selecting a URL. |
App-to-App Secure Channel Communication (multi-device licensing) | The Mobile Authenticator Studio app can receive a secure channel message from a third-party application or web page, display the message content, sign it, and invoke the third-party application or web page with the message signature. |
Multi-language support | The Mobile Authenticator Studio app can be displayed in multiple languages. |
Root detection | On Android and iOS devices, Mobile Authenticator Studio can be configured to prevent execution on rooted or jailbroken devices. By embedding a signature file that lists residual traces of the rooting process, Mobile Authenticator Studio can detect if a device has been rooted. |
Check update | A request can be launched on app startup to check if an update is available. |
SSL pinning | On Android and iOS devices, the Mobile Authenticator Studio app can be configured to use the SSL pinning feature. |
Was this article helpful?