Multifactor Authentication for Site Administrators

Related: User Experience When MFA is Enabled

In this Article:

• Enabling MFA for a Site
• Requiring MFA per User Role
• Reporting on MFA
• Was the MFA Email Sent
• MFA Cookie
• Notes and Known Issues

Enabling MFA for a Site

Visit the Admin > Site Settings page and look in the Authentication section.

Requiring MFA per User Role

• Administrators can require MFA per user role on the Admin > Site Settings page.
• Note well the note shown below the list of user roles: "Users whose role has the API Access permission will not be required to implement MFA."

Reporting on MFA

There are two fields on the System Users table that tie in with MFA. A boolean about whether MFA is enabled and which MFA mechanism in use. A sample report about all users and whether they have MFA enabled can be found in Example Reports.

Was the MFA Email Sent

Emails sent to users using that method appear in the /mail/queue sent list. Add that to the end of your site's URL, for example, foo.legalserver.org/mail/queue. Filter the List Sent Mail list for Subject "verification code".

MFA Cookie

MFA works by storing a cookie named mfa_daily_secret_key in your device's browser. Clearing cookies or other browser data (manually or automatically) will require you to authenticate again.

There are different ways to view cookies in different browsers, but you can see when the current MFA cookie expires. Here is an example using Firefox's Developer Tools:

Notes and Known Issues

• Administrators can see which users have MFA enabled but there is not a way to enable MFA without the user’s participation.
• Users assigned to the Pro Bono Restricted Access role cannot currently use MFA.
• If your organization uses "LinkProtect", "SafeLinks", or some other program that plays with links in your email messages, you may need to manually get the link from within the email message, if you even can. We have tried to work around that software "using up" the one-time use when it follows the link.