Simultaneous activation of several licenses and accounts

Mobile Authenticator Studio can be configured to support multiple authenticator licenses and instances /accounts simultaneously inside the same app. Once the first authenticator account is activated, the user will be able to add a new authenticator account or select an activated authenticator account each time they launch the app.

The licenses share the same parameter set (static vector). Also, each account uses the same graphical and functional customization as well as the same static vector, only the dynamic authenticator data is specific to each account. Once the first authenticator account is activated, the user will be able to add a new authenticator account or select an activated authenticator account each time they launch the app. When deactivated, only the account with the correct serial and sequence number is deactivated.

To enable the activation of multiple accounts the enabled attribute of the MultiInstance element must be set in the Mobile Authenticator Studio configuration.

For multi-device licensing configurations of Mobile Authenticator Studio, the following applies:

1. Loading licenses in the app:

   To load a new license in the app, the user must first scan Activation Message 1 with the new license serial number, and then scan Activation Message 2 that contains the sequence number associated with the license serial number just scanned. Once Activation Message 2 is scanned, the second license is ready to be used in the Mobile Authenticator Studio app. Any message scanned between Activation Message 1 and Activation Message 2 stops the new license loading process.

2. PIN code management:

   When configuring Mobile Authenticator Studio with PIN code protection, the PIN code management is linked to the usage of the Secure Channel feature:

   • If Mobile Authenticator Studio is configured to manage several licenses simultaneously using the Secure Channel feature, each authenticator account is protected with the same PIN code. This PIN code is requested every time an activated account is used or every time a new account is activated

     To prevent collision during PIN validation, the PIN check level must be set to Hash Verification in the Mobile Authenticator Studio Parameter Sheet, and the PIN policy must be set to Reset.

   • If Mobile Authenticator Studio is configured to manage several licenses simultaneously without using the Secure Channel feature, each authenticator account is protected by its own PIN which was provided during the account activation.