Migrating from standard to multi-device licensing

Mobile Authenticator Studio versions prior to 4.3, and Mobile Authenticator Studio version 4.3 that is not configured in multi-device activation mode, can be updated with version 4.4 of a Mobile Authenticator Studio Classic or Premium Edition application configured in multi-device activation mode.

If the value for reactivateOnSVUpdate is false in the application’s configuration file, the application continues to work after the update. In this scenario, the application persists to use the former static and dynamic vectors, which are still stored in the device. The instance of the authenticator is kept unchanged. When the former instance is deleted either with the Delete Instance or the Reactivation process, Mobile Authenticator Studio uses the activation mode as configured in the configuration file.

If the value for reactivateOnSVUpdate is true in the application’s configuration file, Mobile Authenticator Studio displays a warning message to the user. This occurs at the first start after the update, where the formerly activated instances of the authenticator are deleted, and the activation process is started as configured in the configuration file.