Simultaneous activation of several standard licenses

Mobile Authenticator Studio can be configured to support multiple authenticator instances inside the same application. By activating multi-instance support in the configuration file, once the first authenticator instance is activated, end users will be able to add a new authenticator instance or select an activated authenticator instance each time they launch the application.

Multiple-instance support is activated by the enabled attribute of the MultiInstance element in the configuration file. For more information, refer to the Mobile Authenticator Studio Customization Guide.

Each authenticator instance uses the same graphical and functional customization, and parameter set. Only the dynamic authenticator data is specific to each instance.

In this configuration, each authenticator instance uses the same parameter settings. If the parameter settings define that the authenticator is PIN-protected, each authenticator will be protected by its own PIN.

Depending on the Mobile Authenticator Studio configuration, end users can rename or delete each instance in the Settings menu of the application.

Renaming an authenticator instance only affects the text displayed to the end user on launching the Mobile Authenticator Studio application. By default, the name of an instance is its serial number. If the application is not configured to support multiple instances, the instance name will not be displayed. In this case, instance renaming is useless from the end-user perspective. Instance renaming is configured by the enabled attribute of the RenameInstance element in the configuration file. For more information, refer to the Mobile Authenticator Studio Customization Guide.

When an authenticator instance is deleted, the user must confirm the deletion. Once an authenticator instance is deleted, the user can continue to use any of the activated instances or activate a new one. If the deleted instance was the last activated instance, the user is prompted to activate a new instance.

A user cannot activate an instance with the same serial number of an activated instance. Instance deletion is configured by the enabled attribute of the DeleteInstance element in the configuration file. For more information, refer to the Mobile Authenticator Studio Customization Guide.

Instance deletion can be activated even if the application does not support multiple instances. This allows end users to destroy an authenticator without uninstalling and re-installing the application.