Deck Widget
MFA Handling
Most data sources use standard authenticating methods, typically requiring a username and password. However, some sources implement more complex authentication methods to enhance security. Deck Widget is designed to seamlessly support each of these unique authentication methods, ensuring smooth access to data regardless of the source’s requirements.
Deck Widget supports all MFA authentication methods out-of-the-box, with the user able to stay within the Widget experience. You don’t need to configure anything extra for our widget to handle multifactor authentication seamlessly.
Most common types of MFA
| MFA Type | Description |
|---|---|
| One-Time Passcode (OTP) | User selects a phone number and delivery method (text or call) to receive a security code, which is then entered to proceed. |
| Email One-Time Passcode | A code is sent to the user�s email; the user must retrieve and input it to continue. |
| Trusted Device / Push Notification | A notification is sent to a trusted device for confirmation. Common for frequent mobile users. |
| Standard Question | The user must answer a pre-set security question to verify identity. |
| Iterable Question | Users are prompted to update or confirm security questions, often after repeated failed logins or on a schedule. |
Handling Refresh with or without MFA
Once an end-user connects their account, you may need to access refreshed data regularly (e.g., daily, weekly).Refresh flows without end-user presence:
Most refreshes can occur without the end-user�s involvement.When end-user action is required:
- MFA is required: For sources that enforce MFA (e.g., OTP), the user must go through the Widget again.
- Password has changed: If a user updates their credentials, they will need to reauthenticate via the Widget.