Castle's 2FA abides by the TOTP IETF standard. Simply put, a wide range of mobile authenticator apps support 2FA for Castle's dashboard users, including the following:
- Bitium Vault
- Google Authenticator
To set up 2FA on your Castle dashboard account, go to your Account settings page via the dropdown menu in the upper right corner of the dashboard.
Next, select the Security tab. Under the Two-Factor Authentication section, click Enable.
A new tab will open, presenting you with a QR Code to scan with your preferred authenticator app. A manual code is also provided if needed. After scanning the QR Code, enter the one-time password into the text field and click Continue.
You now have 2FA enabled on your Castle account. Next time you are prompted to enter your 2FA code, refer to the authenticator app that you used during configuration.
You can verify that 2FA is set enabled on your account by refreshing your Account Security Settings page and confirming the "disabled" text has changed to "enabled"
Team administrators can check which team members have enabled 2FA on their account by visiting the Team page via the dropdown menu in the upper right corner of the dashboard.
If you are a Castle admin and want to make 2FA required for all members of your organization, please see our article on Setting up Required 2FA for your Castle Org.
Authenticator apps can create multiple entries for accounts within the same service. Since each entry produces a different code, it can be difficult to choose the right one.
If your authenticator app shows multiple entries for Castle, delete any unneeded entries so that you avoid confusion about which one contains the correct code.
Note that there have been reports of problems removing unwanted entries from some iPhone versions of the Google Authenticator app. As of August 2020, reports of these problems persist. If this becomes an obstacle for you, a different authenticator app can be used.
Using Castle on our own dashboard gives us confidence in allowing indefinitely long sessions as long as your device doesn’t look suspicious. Your session will remain open until Castle detects that you deserve to be challenged. The Castle value proposition treats this as a feature in that 2FA friction can be avoided until truly necessary.
Updated about 1 month ago