Setting up MFA for Eclipse Aura

Multi-Factor Authentication (MFA) is an additional layer of security for your Eclipse Aura account. Instead of relying only on your username and password, MFA requires you to verify your identity using a second factor, such as a code from your mobile device.

This helps protect your account even if your password is compromised, ensuring that only you can access your workspace.

Eclipse Aura currently supports:

• Authenticator app codes (via Google Authenticator or Microsoft Authenticator)

• SMS-based codes (sent to your phone via text message)**

** Customer will be changed per SMS at our standard SMS rates. You have mentioned this lower in the article, however they may only read the start.

MFA can be setup per user and database base defaults can be set to enforce MFA requirements.

Linking MFA for each user

Once a dealership staff member has logged in, they can configure their MFA device(s) by editing their user profile (click their name in the top right, then Edit Profile. If the database default MFA has been set, and the staff member hasn't setup the necessary MFA device it will force them upon login.

Click the Security and Login tab, then click manage for the desired type of MFA method and follow the prompts. To use the Authentication App method you need to install the Google or Microsoft Authenticator app.

Adjust individual user MFA settings

When logged in as an administrator you can change the default MFA method per user. Edit the user, click the Security and Login tab, then change the required MFA as desired for that user.

Global MFA Settings

Database wide settings can be found under Settings then System Options, then clicking the Security tab.

MFA Login Default Method

Setting the default method enforces that each user must have this MFA method enabled. If you select QR as the default, the user needs to have this setup, but if you also have MFA SMS Enrollment Allowed they still have the option to use the alternative MFA method.

MFA Login Max Attempt(s)

This is the max failed attempts that can be accepted before the user becomes locked.

MFA Login Remember Device Days

This is the number of days before requiring to entering MFA again for the user - if the user selects "Remember Me" on the given device.

MFA Login Expiry Method

This sets if MFA/login expiry is determined by the last time the MFA was entered (ie. Fixed), or if this date is pushed forward based on the last successful login and the user continues to use the system (ie. Sliding).

Authenticator App Display Name

The name that is displayed for Eclipse Aura for this database in the Authenticator App for the user.

MFA SMS Enrollment Allowed

This allows toggling SMS access on or off. When enabled and SMS is used for authentication, this will incur a charge for each SMS. 

User Email Required for MFA Setup

This enforces login to Eclipse Aura using the staff's email address rather than a username.

SMS Sender Display Name

The name that displayed as the sender for SMS authentication.

Synchronize MFA

If you are using multiple databases on the same server, then linking by login email address. you can copy their MFA device to the other DBs, so when they login they can use the same Authenticator code for all databases. This avoids having to use different authenticator codes to login to different databases.