Okta MFA enabled applications: Automated login with security code in Action logic

If the application you are testing is set up for Okta multi-factor authentication, follow the steps in this article to allow automation logic to acquire verification code when the test is running. The login user id which is used in your test cases should be configured for MFA authentication as described in this article.

Setting up Okta MFA for the test user-id

1. Login to your OKTA account. For the user being configured, reset any existing Okta MFA verification setup as shown below. Navigate to Directory > People > Reset multifactor in the left-nav
   
   
   

2. Log out from the Okta account.

3. Login to Okta again and wait for Okta Verify Setup Page. Click on the Setup button. The same approach works with Google authenticator/Microsoft Authenticator with Okta

4. Choose the appropriate device type and download Okta Verify App (or another Authenticator app that you selected in the above step) on your mobile device and click "Next".
   
5. Click on "Can't Scan?" link below the QR Code 
   
   
   
6. Copy and store the Secret Key. We will need this key as part of our Action logic later.
   
   
   
7. Open Okta Verify App on your mobile device.
   • Click "+" icon
   • Choose "Enter Key Manually" option
   • Enter the secret key displayed on the Okta setup page
   • Click "Add Account".
     
     
   • This will generate a code
8. Enter the code generated in your Okta Verify App in the page below. 
   
   
9. You should have logged into your Okta Account now. 
   
   

Extracting verification code in Action logic

When the application-under-test is set up for multi-factor authentication, you will need to enter a verification code as part of the login process. When you write the logic for Login Action in ACCELQ, insert statements to find and use security code as demonstrated below.

Command: Generate MFA Token from Key

In this command, you will utilize the security key saved in the setup steps. This parameter is encrypted as you type into your Action logic, and hence secure.

In the example below, a typical login process is followed by extraction of the verification code and then applying this code in the application field.