Ezekia

Overview

The security of data in Ezekia is paramount. Two-Factor Authentication (2FA) is now mandatory in Ezekia for firms not using Single Sign-On. It adds an extra layer of security to user accounts by requiring a second form of verification in addition to a password. This greatly reduces the risk of unauthorised access and helps to protect sensitive information. 

This is a short video showing users how to set up Ezekia 2FA.

After setting up 2FA, if you find that you have to enter the 2FA code frequently throughout the day, providing you are on a secure network, you can tick the 'Remember me' box when you sign in, and this will reduce the number of log-ins required.

An alternative to using Ezekia 2FA is for administrators to set up a Single Sign-on solution instead, which will use its own 2FA. If your organisation uses Single Sign-On (SSO) with 2FA enforced by your identity provider, you will not be required to set up or use Ezekia’s 2FA.

 
Set up by Users

To set up 2FA, users must use an authenticator app on their phone. If you don't already have one, they are usually free and can be downloaded from your phone's app store (see the bottom of the article for links to some authenticator apps). 

Google Authenticator is free and is demonstrated in the tutorial video, but other authenticator apps should also work in a similar way.

When you have an authenticator app on your phone, you can sign in to Ezekia. If you have not already added 2FA, you will be prompted to do so. 

The screen will display a QR code. The authenticator app will have a function to add a new entry (Google Authenticator has a 'Plus' icon). Click this and scan the code. This will create a new entry in the app for Ezekia. You can then enter the 6 digit code for Ezekia provided by the authenticator app to prove it is working, and you will be able to use Ezekia normally.

Your administrators can reset your 2FA for you if you lose your phone.

Troubleshooting

If you have a 2FA code set up but it doesn't seem to be working, then the likely cause is that it is stored on an unexpected authenticator app on your phone. The best way forward is for you to: 

1. Ask an administrator to reset your 2FA so that you can start the process again (the instructions for them to do this are in the next section).
2. Make sure any previous ‘Ezekia’ records are removed from your 2FA app. 
3. When scanning the new QR code, ensure you know which app the new record appears in (remember that all authenticator apps work equally well; it doesn't have to be Google Authenticator).

If this doesn't help, please reach out to us, and we will assist in resolving the issue.

Resetting a User's 2FA

Administrators can reset a user's 2FA code if necessary on the settings, permissions page. People with 2FA set have a locked padlock icon on their user profile, as shown below. Click this and accept the confirmation to remove 2FA from that user.

Official Authenticator Links

Here are the official download links for the main authenticator apps on both iOS (App Store) and Android (Google Play). Any one of these can be used as the authorisation app: