CURRENT MOBILE (iOS) – NEW MOBILE (ANDROID)

To perform the migration of the AuthControl Mobile V5 application in its 5.13.0 version to the AuthControl Mobile Authenticator (AMA) application in its 115(1.1.14) version from a mobile with an iOS operating system to another new mobile with the same Android operating system, the following must be carried out Steps:

Step 1: Verify that the AuthControl Mobile V5 app is updated on the device to version 5.13.0, otherwise you will need to run the app update. (Go to the info page of the application and verify that the information it shows you is the one indicated in the figure 62).

Figure 1

Figure 62

If the information shown on the screen of your mobile is different from that presented in figure 62, check step 1 of item 4.2 literal “a”, “b” and “c” to update the application.

Step 2: In the new mobile, download the AuthControl Mobile Authenticator (AMA) app in its 115(1.1.14) version from play store (see figure 63), preconfigure the app so that it is ready for provisioning (review annex 2 as a guide to preconfigure the application).

Figure 1

Figure 63

Step 3: Launch the AuthControl Mobile Authenticator (AMA) app, once on the home page of the app, click on the Menu option located at the top right of the screen (see figure 64).

Figure 1

Figure 64

Step 4: When entering the Menu page, the following options will be displayed on the screen: “Logs”, “About this App”, “Migration” and “App settings”. Click the “Migration” option (see figure 65).

Figure 1

Figure 65

Step 5: The Migration page will be displayed on the screen with two options: “Read QR code from another device (Read QR code)” and “Receive data from the same device (Get Token)” (see figure 66).

Figure 1

Figure 66

Step 6: Press the “Read QR Code” option. Once you have clicked on the “Read QR Code” option, a dialog window is displayed with the Migration Code and two options: “Cancel” and “OK”. Memorize (write down) the Code, click the “OK” option, minimize the application and enter the AuthControl Mobile V5 application (see figure 67).

Figure 1

Figure 67

Step 7: Already in the AuthControl Mobile V5 app on the Menu screen, the following options will be displayed: “Security Code”, “Manual Provisioning”, “Migration”, “E-mail”, “Direct Call” and “Deprovision” (see figure 68 and figure 69).

Figure 1

Figure 68

Figure 1

Figure 69

Step 8: Click on the “Migration” option. Two options will be displayed on the screen: “Create the QR code to read it on another device (Create QR Code)” and “Create the TOKEN and send the data to the same device (Send the data)” (see figure 70).

Figure 1

Figure 70

Step 9: Click on the “Create QR Code” option, a dialog box is displayed for you to enter the Migration code, with the “Cancel” and “OK” options (see figure 71).

Figure 1

Figure 71

Step 10: Enter the code generated by the AuthControl Mobile Authenticator (AMA) app, and press the “OK” option (see figure 72, code we got in step 6, figure 67).

Figure 1

Figure 72

Step 11: The application performs its internal migration process and presents a dialog box asking, Which OS would you want to migrate? With the “ANDROID” and “IOS” options, click on “ANDROID” (see figure 73).

Figure 1

Figure 73

Step 12: Once “ANDROID” is pressed, the app performs an internal process and generates a QR code that must be scanned from the AuthControl Mobile Authenticator (AMA) app on the new mobile (see figure 74).

Figure 1

Figure 74

Step 13: Take the new mobile and press OK in the dialogue window where the Migration Code was presented, the Window with the camera will be displayed to scan the QR Code that was generated in the AuthControl Mobile V5 application (see figure 75).

Figure 1

Figure 75

Step 14: Scan the Code, the app performs its process and indicates that the app was provisioned correctly, otherwise it indicates that it could not be provisioned (see figure 76).

Figure 1

Figure 76

Step 15: The Authcontrol V5 app and the AuthControl Authenticator (AMA) app remain provisioned and synced with the same OATH code on both phones (see figure 77).

Figure 1

Figure 77