About this document
- 23 Oct 2024
- 1 Minute to read
- DarkLight
About this document
- Updated on 23 Oct 2024
- 1 Minute to read
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
How to use this document
You can use this document in different ways, depending on your skill and knowledge level. You can read it from the beginning to the end (highly recommended for novice users), you can browse through the chapter abstracts and read specifically the chapters relevant to your needs, or you can search by key words in the index, if you need to find certain references quickly.
If you need to do the following | Refer to |
|---|---|
...get an introduction to the Mobile Authenticator Studio concepts | |
...get an overview of Mobile Authenticator Studio functionalities | |
...learn more about OTP and e-signature generation with Mobile Authenticator Studio | |
...get information about password protection | |
...get an overview of how users can protect their Mobile Authenticator Studio application with a biometric protection | |
...know more about securely storing data | |
...get an overview of possible activation methods | |
...bind Mobile Authenticator Studio to a particular device | |
...learn more about how Mobile Authenticator Studio can be reactivated | |
...know how to support multiple authenticators | |
...get information about Transaction Data Signing | |
...get information about how to protect the Mobile Authenticator Studio application against attacks during runtime | |
...know more about time synchronization between Mobile Authenticator Studio and the authentication server | |
...know how to display a EULA | |
...know how to display information about the authenticator | |
...know how to auto-launch the Mobile Authenticator Studio application | |
...implement multi-language support | |
...know more about root detection | |
...implement the Check update feature | |
...know more about SSL pinning | |
...get information about how to protect the Mobile Authenticator Studio application against attacks during runtime |
Providing feedback
Every effort has been made to ensure the accuracy and usefulness of this guide. However, as the reader, you are our most important critic and commentator. We appreciate your judgment and would like you to write us your opinions, suggestions, critiques, questions, and ideas. Please send your commentary to: doc-support@onespan.com.
To recognize the particular guide you are referring to, please include the following information in your subject header: OMAS-SA-PG-4.30.9en‑2024-08-20
Please note that product support is not offered through the above email address.
Was this article helpful?