Use Cases
There are nearly unlimited use cases with Auth Armor. Our simple APIs and SDKs make it easy to implement the best and most secure authentication available. Below are a few common use cases.
Passwordless Authentication and Authorization
Obviously, Auth Armor can use used for Passwordless Authentication and Authorization. We can accomplish this with multiple methods. Authentication and Authorization start by needing access to something, then requesting authentication from the user, while presenting the context for the authentication request.
Magiclink Email
You can send an email to a user, and when they click the link, we can authenticate and authorize the user.
Biometric Authenticator
You can send a real-time push notification to a user that explains what is happening and prompts the user for biometric authentication.
WebAuthn
You can request WebAuthn directly from the users registered and trusted device.
2FA/2Factor and MFA
Auth Armor can be used to help protect existing passwords by providing industry leading biometric security with our Biometric Authenticator. Legacy 2FA and MFA currently rely on codes being sent over SMS or generated by an app on a smart device. This is not secure and leads to account take overs and breaches. Step up to something better, more secure and much easier. Instead of users having to type in SMS codes, or find the app and generate a code, simply send a push message to the user and request biometric authentication in real time. It's faster and more secure than legacy 2FA.
Out of Band authentication and authorization
Auth Armor can help you enable and support out-of-band authentication. What is out-of-band authentication (OOBA) you say? It is when you use two methods of communication to perform authentication. For example, most 2FA and MFA solutions can be considered out-of-band because the first authentication takes place on a web browser or app, usually when you ask for a username and password. And the second authentication is a prompt for 2FA codes, and this can be sent over SMS, Email, push message, or generated by an app. This means that there were two communication methods to the user about the authentication.
Auth Armor can help support out-of-band by with Magiclink Email, or our Biometric Authenticator. You can simply use our API to send a request to the user via email or push notification. This is the second line of communication after the user has entered a username or some other identifier on your website, app or service.
Elevation of permissions
Auth Armor can be used to elevate permissions of an already authenticated user. For example, let's say you have already authenticated the user, and the user is logged in to your website app or service. Now the user wants to perform an action that is considered high-security, for example, a large monetary withdraw from an account. You can use Auth Armor to request additional authentication, such as a push message using our Biometric Authenticator, or a magiclink email to the user's email inbox. The practice of elevating permissions is fast, secure and easy with Auth Armor.
Real-time Fraud Prevention
Auth Armor can also help to prevent fraud in real-time. Using our biometric authenticator, you can send real-time push notification alerts to user's mobile devices with details transaction information. The user can then approve or decline the transaction by using biometrics on their mobile device. It's the perfect solution to prevent fraud and it's easy, quick and secure!
Updated about 1 month ago