Futurae Docs
Futurae makes it easy to add usable and strong authentication for your users. In these docs you’ll find everything you need to use our platform.
Developers and businesses can use Futurae to choose from a variety of user authentication technologies in order to secure their web and mobile applications. The Futurae Web widget offers a simple and fast way to integrate Futurae authentication in your web application in a matter of just a few hours.
When further customization and control is required, Futurae’s flexible APIs allow for seamless and fully customizable integration in virtually any software platform.
Which Authentication Options are Available?
Futurae offers a portfolio of authentication factors, which leverage the user’s phone or other mobile devices as software tokens which the user proves possession of during authentication. This is realized by having the user install the Futurae mobile app on his mobile device and enrolling it with his account (except SMS which relies on the user’s mobile phone number). All the available factors can be integrated and used via the Futurae Auth API. The following tables summarize the currently offered factors and their properties.
| Description | |
|---|---|
| One-Touch | One-Touch (also called “Approve”) authentication using a push notification which is sent to the user’s mobile device. |
| Mobile Auth | Single device authentication (i.e., the user is authenticating from a mobile device with an enrolled Futurae mobile app). |
| FIDO2/WebAuthn | Authentication using FIDO2/U2F authenticators via WebAuthn. |
| QR Code | One-Touch authentication using QR code scanning (also known as PhotoTAN). |
| Offline QR Code | Authentication using QR code scanning which works even if the user’s phone is not connected to the Internet. |
| SMS | Authentication via a one-time code which is received via SMS (also known as mTAN). |
| TOTP | Authentication via a time-based one-time code which is retrieved by the Futurae mobile app. |
| HW QR Token | Authentication using hardware tokens based on QR codes. |
| HW TOTP Token | Authentication using hardware tokens based on time-based one-time codes. |
User authentication | Transaction signing | Backend-only integration | Mobile app | Internet connectivity on mobile device | |
|---|---|---|---|---|---|
| One-Touch | Yes | Yes | Yes | Yes | Yes |
| Mobile Auth | Yes | Yes | Yes | Yes | Yes |
| FIDO2/WebAuthn | Yes | No | No | No | No |
| QR Code | Yes | Yes | Yes | Yes | Yes |
| Offline QR Code | Yes | Yes | Yes | Yes | No |
| SMS | Yes | Yes | Yes | No | No* |
| TOTP | Yes | No | Yes | Yes | No |
| HW QR Token | Yes | Yes | Yes | No | No |
| HW TOTP Token | Yes | No | Yes | No | No |
* SMS does not require Internet connectivity on the phone, but it still requires the ability to receive SMS messages.
Requirements
Some of the authentication technologies offered by Futurae, such as One-Touch, require the installation and usage of the Futurae mobile app, Futurae WhiteLabel apps or Futurae mobile SDKs that can be used to integrate the Futurae authentication technologies in your own mobile app. These mobile components are available on the following platforms:
- Futurae App Android (minimum required OS version: Android 6 Marshmallow – API Level 23).
- Official Play Store URL: https://play.google.com/store/apps/details?id=com.futurae.mobileapp
- Futurae App iOS (minimum required OS version: iOS 12).
- Official App Store URL: https://itunes.apple.com/us/app/futurae/id1069858990?mt=8
- Futurae WhiteLabel App Android (minimum required OS version: Android 6 Marshmallow – API Level 23).
- Futurae WhiteLabel App iOS (minimum required OS version: iOS 12).
- Futurae Mobile SDK Android (minimum required OS version: Android 6 Marshmallow – API Level 23).
- Futurae Mobile SDK iOS (minimum required OS version: iOS 11).
The authentication technologies offered by Futurae are supported on all browsers, except FIDO2/WebAuthn authentication which is only available on browsers that support WebAuthn.
Where to Go Next?
If you are looking to integrate Futurae authentication in your web application, make sure to check out the Futurae Web widget option, which offers the easiest and fastest approach, however at the cost of customizability.
If your authentication use case requires further tailoring and customization options, then the Auth API is probably a better option for you, and we suggest that you begin by reading our guide on how to implement the Auth API. For further user and device administration functionality, as well as various analytics, checkout the Admin API.