This topic refers to functionality that is not available to accounts on the Quick Base Essential plan. If the functionality described here does not match what you're seeing in Quick Base, your account is probably on this plan.
With 2-step authentication, a user signing in to Quick Base must provide two means of identification from separate categories of credentials: username/password combination and a security code provided via email. When this option is enabled, if the user enters a valid username and password, they are then prompted to enter their security code.
Only native Quick Base users can use 2-step authentication. If you have a mix of SAML and native Quick Base users you can enable 2-step for just the native users. However, if you have a mix of LDAP and native Quick Base users you can NOT enable 2-step for native users.
How you turn on 2-step authentication depends on your account configuration, as described below.
For an account that is part of a realm, if an admin wants to enable 2-step authentication and opens the Summary tab of the Manage Account Billing page, they are directed to require 2-step authorization on the realm Policies tab.
On the My Apps page, click Manage name_of_realm then click the Policies tab.
Select Require 2-step authentication.
On the My Apps page, click Manage name_of_realm.
Click the Summary tab.
Click Edit Account Properties.
Select Require 2-Step Authentication.
When you sign in to Quick Base with 2-step authentication enabled, Quick Base prompts you to enter the verification code that was sent to your email.
Sign in to Quick Base. You'll see this dialog:
Enter the code you received via email. This is a six-digit alphanumeric code, e.g.:Y7X4QN
Check Remember this device for 30 days and you'll be able to sign-in without entering a code for 30 days.
Verification codes are good for 10 minutes. To request another email with a new code, click the I didn't get an email link.
Note: With 2-step authentication enabled, users already signed in won't be prompted to enter a code until their authentication ticket has expired.
Quick Base connected tables can be used with 2-step authentication by enabling user token authentication. To make a connection to a Quick Base app that uses 2-step authentication, add a user token for the source app and then use that user token to make the connection. For more on user tokens and connected tables, read Connecting to another Quick Base app.
Any API integrations must authenticate using user tokens and not standard Quick Base API_Authenticate. If you are using API_Authenticate, the integration will fail.
Verification codes are good for 10 minutes. If you enter an expired code, you'll return to the sign in page and see this message:
If you did NOT enter the code but it has nevertheless expired, you'll see this message:
If you enter an incorrect code, you'll see this message:
If you enter an incorrect code more than 3 times, you'll see this message:
© 1999-2018 QuickBase, Inc. All rights reserved. Legal Notices.