Uploaded image for project: 'Moodle QA'
  1. Moodle QA
  2. MDLQA-18925 Moodle 4.5 QA
  3. MDLQA-19364

CLONE - Multi-Factor Authentication - SMS factor exploratory test

XMLWordPrintable

      This is an exploratory test of a new feature or improvement, so please feel free to try anything you like and not just the test steps!

      Prerequisites

      • This test requires admin access and access to terminal to run CLI commands, as part of the testing will lock out a user from accessing the site.
      • You will need a resource for testing SMS sending in AWS (if you are an HQ team member testing this, feel free to reach out to the Platform team who may be able to help with access to an AWS sandbox for testing).
      • You will require one site on Moodle 4.4, and another brand new site on 4.5.
      • You will require admin access to both Moodle sites.
      • You will want to have CLI access to the sites, to recover from any account lockout.

      Troubleshooting

      IMPORTANT: If you locked yourself out, you can disable the whole MFA plugin from the CLI:

      php admin/cli/cfg.php --component=tool_mfa --name=enabled --set=0

      Test Mobile phone SMS Authentication (upgrade):

      1. Log into your Moodle 4.4 instance as admin.
      2. Navigate to: Site administration > plugins > admin tools > Multi-factor authentication.
      3. Enable the "MFA plugin enabled" checkbox and save.
      4. Find "SMS mobile phone" in the list of factors and press Settings.
      5. Enable the factor and set it up with the provided AWS credentials.
      6. Checkout 4.5 (main) and upgrade the site.
      7. Navigate to: Site administration > plugins > admin tools > Multi-factor authentication.
      8. Confirm you can see the new setting SMS gateway.
      9. Confirm the SMS gateway setting has the following option selected: MFA AWS (AWS).
      10. Navigate to: Site administration > plugins > SMS > Manage SMS Gateways.
      11. Confirm you can see the following gateway in the table: MFA AWS (AWS).
      12. Click the toggle to disable the gateway.
      13. Confirm you can see the notification that it's in use and cannot be disabled.
      14. Click the Delete action to delete the gateway.
      15. Confirm you can see the notification that it's in use and cannot be deleted.
      16. Click the Edit action to edit the gateway.
      17. Confirm you can see the same credentials you previously set up in MFA (to confirm they migrated successfully).
      18. Access your user preferences / "Multi-factor authentication preferences".
      19. Set up the "SMS mobile phone" factor with your mobile phone number.
      20. Confirm you have received an SMS on your phone.
      21. Enter the code you received where prompted in Moodle and continue.
      22. Open a second browser (either a different browser, or a private/incognito session, so it is not currently logged in) and access Moodle with your user.
      23. Enter your username and password.
      24. Confirm a new screen is displayed where it asks for the Mobile phone SMS.
      25. Confirm you have received an SMS on your phone.
      26. Enter the code in the box and click on verify code.
      27. Confirm you are logged successfully and you have access to Moodle.
      28. Run cron.
      29. Once logged in as admin, open notifications and confirm that you received the notification about the migration of the SMS gateway instance.

      Test Mobile phone SMS Authentication (fresh install):

      1. Stand up a Moodle main (4.5) instance.
      2. Access to your Moodle as admin user.
      3. Navigate to: Site administration > plugins > admin tools > Multi-factor authentication.
      4. Enable the "MFA plugin enabled" checkbox and save.
      5. Find "SMS mobile phone" in the list of factors and press Settings.
      6. Confirm you are prompted to set up an SMS gateway.
      7. Follow the link "set up an SMS gateway".
      8. Fill all the fields using the AWS credentials provided previously.
      9. Save changes.
      10. Confirm you are redirected back to the SMS mobile phone settings for MFA, and config options are now available.
      11. Navigate to: Site administration > plugins > SMS > Manage SMS Gateways.
      12. Click the toggle to disable the gateway.
      13. Confirm that the gateway is disabled.
      14. Click the Edit action.
      15. Change the name of the gateway.
      16. Confirm that the gateway is updated with the new name.
      17. Click the Delete action.
      18. Select continue button in the dialogue.
      19. Confirm that the gateway is deleted.
      20. Create another SMS gateway using the same AWS credentials.
      21. Navigate to: Site administration > plugins > admin tools > Multi-factor authentication.
      22. Find "SMS mobile phone" in the list of factors and press Settings.
      23. Confirm you can see the newly created SMS gateway in the list of SMS gateways.
      24. Select the created SMS gateway in the SMS gateway setting.
      25. Enable the factor and confirm you can then set the factor weight and secret validity duration.
      26. Fill those with the default values and save changes.
      27. Set up the "SMS mobile phone" factor with your mobile phone number.
      28. Confirm you have received an SMS on your phone.
      29. Enter the code you received where prompted in Moodle and continue.
      30. Open a second browser (either a different browser, or a private/incognito session, so it is not currently logged in) and access Moodle with your user.
      31. Enter your username and password.
      32. Confirm a new screen is displayed where it asks for the Mobile phone SMS.
      33. Confirm you have received an SMS on your phone.
      34. Enter the code in the box and click on verify code.
      35. Confirm you are logged successfully and you have access to Moodle.
      36. You may want to also test a student can follow the same process and log in with SMS as a second factor.

        1. MDLQA-19364 1-11.png
          MDLQA-19364 1-11.png
          42 kB
        2. MDLQA-19364 1-15.png
          MDLQA-19364 1-15.png
          57 kB
        3. MDLQA-19364 1-21.png
          MDLQA-19364 1-21.png
          62 kB
        4. MDLQA-19364 1-22.png
          MDLQA-19364 1-22.png
          45 kB
        5. MDLQA-19364 1-27.png
          MDLQA-19364 1-27.png
          68 kB
        6. MDLQA-19364 1-28 fail.png
          MDLQA-19364 1-28 fail.png
          17 kB
        7. MDLQA-19364 1-28 PASS.png
          MDLQA-19364 1-28 PASS.png
          24 kB
        8. MDLQA-19364 1-28 PASS-1.png
          MDLQA-19364 1-28 PASS-1.png
          24 kB
        9. MDLQA-19364 1-6.png
          MDLQA-19364 1-6.png
          110 kB
        10. MDLQA-19364 1-8.png
          MDLQA-19364 1-8.png
          96 kB
        11. MDLQA-19364 2-13.png
          MDLQA-19364 2-13.png
          42 kB
        12. MDLQA-19364 2-16.png
          MDLQA-19364 2-16.png
          42 kB
        13. MDLQA-19364 2-19.png
          MDLQA-19364 2-19.png
          41 kB
        14. MDLQA-19364 2-23.png
          MDLQA-19364 2-23.png
          78 kB
        15. MDLQA-19364 2-25.png
          MDLQA-19364 2-25.png
          108 kB
        16. MDLQA-19364 2-27.png
          MDLQA-19364 2-27.png
          47 kB
        17. MDLQA-19364 2-27-1.png
          MDLQA-19364 2-27-1.png
          47 kB
        18. MDLQA-19364 2-32.png
          MDLQA-19364 2-32.png
          46 kB
        19. MDLQA-19364 2-36.png
          MDLQA-19364 2-36.png
          48 kB
        20. MDLQA-19364 2-361.png
          MDLQA-19364 2-361.png
          67 kB
        21. MDLQA-19364 2-362.png
          MDLQA-19364 2-362.png
          61 kB
        22. MDLQA-19364 2-362-1.png
          MDLQA-19364 2-362-1.png
          61 kB
        23. MDLQA-19364 2-363.png
          MDLQA-19364 2-363.png
          77 kB
        24. MDLQA-19364 2-363-1.png
          MDLQA-19364 2-363-1.png
          77 kB
        25. MDLQA-19364 2-364.png
          MDLQA-19364 2-364.png
          47 kB
        26. MDLQA-19364 2-364-1.png
          MDLQA-19364 2-364-1.png
          47 kB
        27. MDLQA-19364 2-365.png
          MDLQA-19364 2-365.png
          35 kB
        28. MDLQA-19364 2-6.png
          MDLQA-19364 2-6.png
          56 kB

            lameze Simey Lameze
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.