Mobile Application V5 to AMA¶
User Manual for Migrate the Mobile Application from V5 version to AuthControl Mobile Authenticator (AMA)
Overview¶
Swivel Secure, always thinking of providing its clients with technological applications that continue to maintain high security standards, set out to create new mobile applications that continue to provide the benefits of its V5 mobile application. Always thinking about improving the experience of our users, the following manual contains the steps to carry out the migration of the mobile application AuthControl Mobile V5 to the AuthControl Mobile Authenticator (AMA) version on mobile phones with Android and iOS operating systems.
Migration¶
Before starting the process to migration, the AuthControl Mobile V5 application to the AuthControl Mobile Authenticator (AMA) version, the user must be clear about the following aspects:
- The migration will be executed on the current mobile where the V5 application is installed and operational.
- The migration will be executed to a new mobile.
For both cases, the user must identify the process to follow according to the operating system of the current mobile and new mobile. Below is a table corresponding to cases 1 and 2 (stated above), where you can identify the number of the item that you must read and follow step by step to execute the migration of the application.
| Current Mobile (Android OS) | Current Mobile (IOS OS) | ||
| Case 1 - Current Mobile | Item 4.1 | Item 4.2 | |
|
Android | Item 5.1 | Item 5.3 |
| IOS | Item 5.2 | Item 5.4 | |
Case 1 - Current Mobile¶
Requeriments
To carry out the migration from AuthControl Mobile V5 to the AuthControl Mobile Authenticator (AMA) application, it is a mandatory requirement that the AuthControl Mobile V5 application is provisioned under the “Local OATH” configuration policy, if provisioned under any other configuration policy for example “OATH Online” or “PIN” you will need to contact your system administrator to make the required change in the provisioning.
Case 2 - New Mobile¶
Requeriments
To carry out the migration from AuthControl Mobile V5 to the AuthControl Mobile Authenticator (AMA) application, it is a mandatory requirement that the AuthControl Mobile V5 application is provisioned under the “Local OATH” configuration policy, if provisioned under any other configuration policy for example “OATH Online” or “PIN” you will need to contact your system administrator to make the required change in the provisioning.
5.1 - Current Mobile (Android) - New Mobile (Android)
5.3 - Current Mobile (Android) - New Mobile (IOS)
Preconfigure AuthControl Mobile¶
Android¶
Figure 94
- Welcome to the AC Mobile Authenticator (press Next).
- Please give us access to your camera (press PERMISSION).
- Allow AC Mobile Authenticator to take photos and record videos? (Press Allow o Reject).
- Allow AC Mobile Authenticator to access photos, media files, etc on your device? (Press Allow o Reject).
- Please give us access to your camera (press PERMISSION).
- Please give us access to your biometrics (press PERMISSION).
- Ok, your app is READY to use. (Press DONE).
- Welcome to AuthControl Mobile Authenticator.
IOS¶
Figure 95
- Welcome to the AC Mobile Authenticator (press Next).
- Please give us access to your camera (press PERMISSION).
- Allow AC Mobile Authenticator to take photos and record videos? (Press Allow o Reject).
- Allow AC Mobile Authenticator to access photos, media files, etc on your device? (Press Allow o Reject).
- Please give us access to your camera (press PERMISSION).
- Please give us access to your biometrics (press PERMISSION).
- Ok, your app is READY to use. (Press DONE).
- Welcome to AuthControl Mobile Authenticator.