CURRENT MOBILE (ANDROID) – NEW MOBILE (iOS)

To perform the migration of the AuthControl Mobile V5 application in its 5.4.2 version to the AuthControl Mobile Authenticator (AMA) application in its 7.0.0 version from a mobile with an Android operating system to another new mobile with iOS 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.4.2, 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 45).

Figure 1

Figure 45

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

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

Figure 1

Figure 46

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 47).

Figure 1

Figure 47

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

Figure 1

Figure 48

Step 5: In 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 49).

Figure 1

Figure 49

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 50).

Figure 1

Figure 50

Step 7: Enter the AuthControl Mobile V5 app, on the home screen where the OATH code is displayed, click on the options menu at the top left of the screen, the following options will be displayed: “OATH”, “Information”, “About”, “Settings”, “Migration”, “Email” and “Direct call” (see figure 51 and figure 52).

Figure 1

Figure 51

Figure 1

Figure 52

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 53).

Figure 1

Figure 53

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

Figure 1

Figure 54

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

Figure 1

Figure 55

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 “iOS” (see figure 56).

Figure 1

Figure 56

Step 12: Once “iOS” 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 57).

Figure 1

Figure 57

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 58).

Figure 1

Figure 58

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 59 and figure 60).

Figure 1

Figure 59

Figure 1

Figure 60

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 61).

Figure 1

Figure 61