OTP codes can be produced using either an authentication app (on a Android or a iOS mobile device), a desktop app, or using a programmable hardware token.
Before you can produce OTP codes that can be used during authentication, you will need to obtain seed data from your administrator (this will normally be in the form of a QR code but may alternately be in the form of base32 or hex encoded seed data).
Installing a Google Authenticator Compatible Mobile App
The following example demonstrates how a user can prepare for OTP code generation using SafeID authenticator App using an Android or IOS smartphone;
Whilst the Google Authenticator app is available for Android and IOS, it is not presently available for desktop or laptop computers.
You can however use the SafeID authenticator app on all three platforms (and the procedure for these solutions is very similar).
The SafeID app is compatible with Google Authenticator software tokens so we whilst the following instructions explain how to prepare for OTP authentication using SafeID app on windows, the instructions are essentially the same in all versions.
First we need to download the app (using the store appropriate to your hardware), and once the app has been installed and launched you will be asked if the app is to be PIN protected;
PIN protection is optional, and if not needed can be skipped by clicking "Continue without PIN".
You will be asked if log capturing is to take place - again this is optional and can be skipped;
Finally you will be asked to sign in to your account (if you don't have an account yet on can be set up using the "Set up my account" button).
If a new account is set up you will need to verify the account, and once this is done you will be presented with a currently empty list of tokens;
At this point you are ready to add a token using the icon;, or the "Add Token" option under the ellipsis icon ("...");
Once you have selected to add a token you will be presented with two options by which the token can be added;
Now that the applications have been prepared we need to add a token (this may be performed either using a QR code, or manually);