Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
gettingstarted:2fa:2fa_two_factor_authentication [2025/03/13 20:43] – created chad | gettingstarted:2fa:2fa_two_factor_authentication [2025/07/29 16:16] (current) – [Setup] grant | ||
---|---|---|---|
Line 9: | Line 9: | ||
To set up go to www.t4login.com and login with your firm, username, and password. Once logged into the user setup web page you will see a new link called "Setup Security" | To set up go to www.t4login.com and login with your firm, username, and password. Once logged into the user setup web page you will see a new link called "Setup Security" | ||
- | Image | + | {{: |
- "Setup Security" | - "Setup Security" | ||
Line 27: | Line 27: | ||
If two-factor authentication is not enabled for the user until they successfully verify their phone number/ | If two-factor authentication is not enabled for the user until they successfully verify their phone number/ | ||
- | Image | + | {{: |
- | Image | + | {{: |
===== Usage===== | ===== Usage===== | ||
Line 38: | Line 38: | ||
- | Image | + | {{: |
If the user has not 2FA authorized this device yet, then the user will be sent a 6-digit authorization token and the application will prompt for it: | If the user has not 2FA authorized this device yet, then the user will be sent a 6-digit authorization token and the application will prompt for it: | ||
- | Image | + | {{: |
Once the user enters the 6-digit code, the users’ device will be considered “authorized” and this second step will not be required again. | Once the user enters the 6-digit code, the users’ device will be considered “authorized” and this second step will not be required again. | ||
Line 50: | Line 50: | ||
The screen that prompts for the authentication code will display a link to send the code to email instead after a 20-30 second delay: | The screen that prompts for the authentication code will display a link to send the code to email instead after a 20-30 second delay: | ||
- | ===== Versions older than 4.3.72.1 ===== | ||
- | 2FA is supported for all older version of T4 and apps written to older versions of our API. | ||
- | When the user logs in using an old version, the login will fail, however an authentication token will be delivered to the user. | ||
- | |||
- | Image | ||
- | |||
- | Image | ||
- | |||
- | As the message explains, the user needs to append the 6-digit code to his password on the next login attempt. | ||
- | |||
- | So if the users’ password is “g01ng8roke”, | ||
===== Non-Supported Applications ===== | ===== Non-Supported Applications ===== | ||
Two-factor authentication is not possible in cases where we cannot receive a unique device identifier. FIX API applications are a good example. | Two-factor authentication is not possible in cases where we cannot receive a unique device identifier. FIX API applications are a good example. |