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.
|Zero-Touch||Zero-Touch (also called SoundProof) authentication by transparently verifying proximity of the user’s mobile device and the device on which the authentication takes place. Zero-Touch leverages background ambient sounds, coupled with near-ultrasound emission in order to verify proximity of the two devices.|
|Zero-Touch Jingle||Zero-Touch authentication with an audible jingle being played during authentication. Ideal for authentication on conversational interfaces, such as Amazon Alexa.|
|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).|
|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.|
Internet connectivity on mobile device
|Offline QR Code||Yes||Yes||Yes||Yes||No||No|
* The device which is going to be used for a particular authentication attempt needs to be specified, in case the user has multiple enrolled devices ("auto" option is available, which automatically uses the user's most recently enrolled device).
** SMS does not require Internet connectivity on the phone, but it still requires the ability to receive SMS messages.
The authentication factors offered by Futurae, except SMS, require the installation and usage of the Futurae mobile app. The Futurae mobile app is available on the following platforms:
- Android (minimum required version: Jelly Bean 4.3.x – API Level 18).
- Official Play Store URL: https://play.google.com/store/apps/details?id=com.futurae.mobileapp
- iOS (minimum required version: iOS 10).
- Official App Store URL: https://itunes.apple.com/us/app/futurae/id1069858990?mt=8
As an alternative option, we offer a mobile SDKs for Android and iOS, in order to integrate the Futurae authentication technologies in your own mobile authenticator app.
The authentication factors offered by Futurae, except Zero-Touch, are supported on all browsers.
Zero-Touch (SoundProof) authentication, in particular, is supported on the following browsers:
- Google Chrome
- Microsoft Edge
- Mozilla Firefox
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.
If your authentication use case require 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.