everal mobile apps, including Google Authenticator, Microsoft Authenticator, Sophos Authenticator etc, are basically a simple application that generates either time-based or event-based one-time passwords (OTP) according to RFC 6238 and RFC 4226. DualShield supports both the time-based and event-based one-time passwords (OTP) according to RFC 6238 and RFC 4226. Therefore, any app or token that is compliant with RFC 6238 and RFC 4226 can be used with DualShield. 

By default set up, DualShield includes Google Authenticator as one of OTP authenticartors. If you are using one of other OTP authenticator apps that is compatible with Google Authenticator, such as Microsoft Authenticator and Sophos Authenticator, then you can simply use Google Authenticaror in DualShield to support your authenticator apps. However, if you want to avoid any confusion because of the name, then you can actually create a custom authenticator product in DualShield with the exact name that you would like, such as "Microsoft Authenticator" or "Sophos Authenticator", for instances. This guide explains how to create in DualShield a custom authenticator product that's compatible with Google Authenticator.

Login to DualShield management console, select Authentication | Products, then in the Product tab click the Create button on the toolbar. A window with the title Product Info – New will pop up.

Algorithm -  select "OATH/TOTP"

Manufacturer Code - you must enter "GG" in this box

Product Code - you can enter a short code that represents the authenticator app, such as "MST" for "Microsoft Authenticator - Time Based" 

Name - enter the name of the authenticator app, such as "Microsoft Authenticator"

Model - enter "Time-Based"

Functions - select "Logon"

Form Factor -  select "Software"

Provisioning - Select "Download"

Time Window - Enter "30"

Digits - enter "6"

Crypto - select HmacSHA1 


Click Save to save the new authenticator product.

Now, you can create tokens of this newly added authenticator