Offline activation

Similar to online activation, offline activation consists in providing the activation data. With this type of activation, the activation data is split. The configuration data resides in the Mobile Authenticator Studio app, whereas the key of the authenticator is entered by the user through the activation code. Therefore, the serial number and activation code need to be securely delivered to users prior to the activation (e.g. in a sealed letter).

In addition to the activation code, users need to provide the serial number, which is necessary to rebuild the key of the authenticator from the activation code. The authenticator's serial number and activation code are delivered to the integrator in the DPX file, as specified in theMobile Authenticator Studio Parameter Sheet.

Offline activation

Instead of entering a serial number (e.g. FDM1280189), the user could enter a serial number suffix (e.g. 1280189). However, this is not recommended because the serial number prefix will be retrieved from the static vector. Thus the serial number prefix can differ from the static vector that is hardcoded in the mobile app (e.g. FDL) and the authenticator BLOBs used by the server (e.g. FDM). In this case, the authenticator account (i.e., an instance of the authenticator) will be properly activated, but the generated authenticator responses (i.e. OTP and signature) will be invalid.

If reactivation with event reactivation counter (ERC) is enabled, a field to enter the ERC will be displayed in the offline activation screen. For more information, see Reactivation of a standard license.