Medable employs session-based (using cookies) and signature-based authentication. Within each org, applications can be created which provide the necessary key and secret for API access.
For more information on Cortex authentication, see Authentication
As one of the many technical safeguards built into Medable, two-factor authentication helps ensure security and compliance so as a user you can be sure no one can gain access to your sensitive data and as a company, you can be sure that your users are who they say they are.
Two-factor authentication is automatic and always on. When Medable detects that a user is authenticating from a new location or device, a verification code is sent to the mobile number for that user. The user simply has to provide that authentication code to be authenticated and for the new location or device to be verified.
The process looks like this:
An example of this in use can be seen right from the login screen for your org's control panel. Here we'll attempt to login to the control panel from a new device.
However, Medable detects that we're logging in from a new location so authentication doesn't happen. Instead we're presented with the same login form but a new field to enter in our verification code.
Checking our mobile device, we receive the verification code via SMS.
We simply have to enter that code into the login form and now we're able to sign-in.
You don't have to do anything to enable 2FA in the API. It works automatically when a user authenticates. However, you do want to be sure to build in the right interface and user-experience in your app for 2FA exception handling.
When authenticating via the API, if 2FA is initiated, you will receive a
kNewLocationfault in the response:
"message":"A new location has been added to the account. Please verify it"
At this point the user will be sent their verification code via SMS. You can use the
kNewLocationfault to trigger your UI to present the user with the verification code field.
Then, the token will need to be passed in the second authentication request:
With location.verificationToken sent, the location is verified and authentication is successful. Future authentication attempts from this location will not require 2FA.
Two-factor authentication does require the user to take an extra step in order to authenticate. However, most users rarely run into it in day-to-day use. This is because when a user registers their account, the device they register from is automatically verified. So if the user typically uses the app on one device, 2FA will never be initiated. Only if the user logs in from a different device or deletes and re-installs the app will the 2FA process initiate.
It's also important to note that this extra step is there to help ensure that the user's data is secure. Often when this added level of security is explained to users, it is seen as a positive.
Typically the only users that are negatively impacted by 2FA are developers since developers often need to test apps from multiple accounts and devices. Because of this, we allow for bypassing 2FA by adding email address for developers to the
Location Verification Bypasssetting under
Settings > Organizationin the control panel (see Organization Settings for more info).