inWebo MFA platform and solutions:
Providing an authentication technology (authentication methods & validation methods) only solves a tiny part of the questions faced by an organization deploying multi-factor authentication. inWebo solutions, implemented by our platform, consist in:
-Authentication methods for the users
-A dedicated authentication account for your organization on our platform
-Connectors and pre-integrated modules to link the applications needing MFA and the organization account
-Users and devices management tools: on-boarding workflow, support interface, usage logs
-A full API and a webconsole to configure and manage the organization account
-An optional directory synchronization tool to automate user management
2-step verification, 2-factor authentication, local authorization:
2-step verification: if you use inWebo as an additional security layer implemented on top of your existing authentication infrastructure (Active Directory for instance), there’s probably no need to ask the user for a second secret. Therefore we recommend to configure OTP to depend only on a trusted device; inWebo manages the second layer of authentication only.
2-factor authentication: alternatively, if you replace the complete authentication process with inWebo, we’ll take care of both layers, such as a user secret (not linked to the Active Directory password) and a user trusted device. You no longer need to store user credententials in your infrastructure.
Local sign-in: this covers somewhat different use cases. A first category includes paired use cases where a user signs in to a computer using a smartphone and opens a local session or a session on a Windows domain. It also covers unpaired use cases where a user requests access with a specific usage context (time, duration…) using a smartphone to a shared object such as a rental car, a door lock, etc., and is granted authorization locally.