Activate Multi Factor Authentication (MFA) for your admin user

The first thing you'll do before you dive into your account configuration is activating Multi Factor Authentication for your admin user. For more information, follow the instruction below.

Take note: When your a new customer to Realtime Register (Accounts created after 04-30-2020) you're required by policy to enable MFA for (all) your user(s). You will not be able to use any functionality on our registrar platform unless you first configure multi factor authentication. As a result of the requirement to setup MFA, navigating to any of the menu options on the left side of the Domain Manager will redirect you back to the configuration page to setup MFA. Once MFA is setup for your admin users, the menu options will regain their normal functionality you can follow the complete default account configuration instruction to setup your account for first use.

You can implement MFA by either using an Authenticator app or a security key. For a detailed instruction on both options, continue reading below.

Authenticator app
Security key

Authenticator app

By Default, your account holds only one user, the "admin" user. You're going to configure MFA for this user and from there on out you can force MFA for the other users your going to add. More information on activating MFA for other users in your account will be detailed later on in the default account configuration process.

Take note: The below instruction from here on out can be used for other users than your admin user as well.

Login to the Domain Manager and go to Account details > Users

  • Click the green "Activate authenticator app" button to start enabling MFA to your Realtime Register account.

  • A screen with recovery codes pops up, download or copy the recovery codes before continuing to the next step. The recovery codes enable you to login to your account in the event you cannot access your account with MFA. Once saved, click "Next".

Take note: If another MFA method already is active, you will not be prompted with the recovery code screen.

Take note: Treat your recovery codes with the same level of attention as you would your password! We recommend saving them with a password manager such as Lastpass, 1Password, or Keeper.

  • In the next step, you will pair an authenticator app. Just pop up one of the supported authenticator apps on your phone and follow the respective procedure from your app of choice to enable the authenticator app for use with your Realtime Register account. If the QR-code is for some reason not scan-able or not read-able by your method of choice, click the "unable to scan" button complete this step manually.

Take note: Supported authenticator apps are the Google Authenticator or Authy app available in the app store on your device. Alternatively, you can also install a browser plugin to act as authenticator app.

  • You've now successfully activated an authenticator app to use for MFA for the admin user of your Realtime Register account and can use it to login.

Take note: If you for any reason lose access to your MFA device or app that is connected to your admin user, you can always use one of the recovery keys to login. Once all recovery keys have been used you will no longer have access to your account. If this occurs, contact Realtime Register support through support@realtimeregister.com to gain access to your account again.


Security key

By Default, your account holds only one user, the "admin" user. You're going to configure MFA for this user and from there on out you can force MFA for the other users your going to add. More information on activating MFA for other users in your account will be detailed later on in the default account configuration process.

Take note: The below instruction from here on out can be used for other users than your admin user as well.

Login to the Domain Manager and go to Account details > Users

  • To setup a security key as MFA, click the green "Setup security key" button.

  • A screen with recovery codes pops up, download or copy the recovery codes before continuing to the next step. The recovery codes enable you to login to your account in the event you cannot access your account with MFA. Once saved, click "Next".

Take note: If another MFA method already is active, you will not be prompted with the recovery code screen.

Take note: Treat your recovery codes with the same level of attention as you would your password! We recommend saving them with a password manager such as Lastpass, 1Password, or Keeper.

  • Submit the name for your security key and click the green "Register security key" button.

Take note: !!When using applications like Krypton, it's necessary to have krypton paired to the browser you use to successfully pair a security key!! Otherwise, the below steps will not be possible to complete.

  • You'll now be prompted with the message to tap your security key or insert your security key into the USB port of your device. Insert your choice of key and the process will complete automatically.

Take note: when using krypton for example a push message will be send to your mobile device that is paired to your browser. Accept the message and you will setup the security key.

  • You've now successfully added a security key to use for MFA for the admin user of your Realtime Register account and can use it to login.

Take note: If you for any reason lose access to your security key that is connected to your admin user, you can always use one of the recovery keys to login. Once all recovery keys have been used you will no longer have access to your account. If this occurs, contact Realtime Register support through support@realtimeregister.com to gain access to your account again.

Known issues

The below example originates from a successfully paired krypton security key. Currently, krypton has an issue that causes the Windows security warning to remain on screen until you dismiss it from your screen. This will have no influence on the quality and security of your security key, but is a mere visual glitch which krypton is working on to fix.


Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us