Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-61622

New Web Service for checking if age digital consent verification is enabled

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 3.3.4, 3.4.1, 3.5
    • Fix Version/s: 3.3.5, 3.4.2
    • Component/s: Authentication
    • Labels:
    • Testing Instructions:
      Hide

      To be tested in Moodle 3.3, 3.4 and 3.5

      1. Open the system console
      2. Execute the following command, replacing the Moodle URL with your own one.

        curl 'http://localhost/m/stable_master/lib/ajax/service.php?sesskey=pEz3ihR1lC' --data-binary '[{"index":0,"methodname":"core_auth_is_age_digital_consent_verification_enabled","args":{}}]' | python -m "json.tool"

      3. If in the response data->status is set to true it means that the setting "Digital age of consent verification" in Administration > Plugins > Authentication >Manage authentication is set to "Yes"
      4. If in the response data->status is set to false, it means that the setting is set to "No"

      To be tested in Moodle 3.5 (master)

      1. Set the setting "Digital age of consent verification" in Administration > Plugins > Authentication >Manage authentication to "Yes"
      2. Execute the following command, replacing the Moodle URL with your own one.

        curl 'http://localhost/m/stable_master/lib/ajax/service.php?sesskey=pEz3ihR1lC' --data-binary '[{"index":0,"methodname":"tool_mobile_get_public_config","args":{}}]' | python -m "json.tool"

        1. Check that the fields:
          • data->agedigitalconsentverification is set to true
          • data->supportemail is set to the same value than the Moodle site (use the Site administration search and look for supportemail to check the value)
          • data->supportname is set to the same value than the Moodle site (use the Site administration search and look for supportname to check the value)
      Show
      To be tested in Moodle 3.3, 3.4 and 3.5 Open the system console Execute the following command, replacing the Moodle URL with your own one. curl 'http://localhost/m/stable_master/lib/ajax/service.php?sesskey=pEz3ihR1lC' --data-binary ' [{"index":0,"methodname":"core_auth_is_age_digital_consent_verification_enabled","args":{}}] ' | python -m "json.tool" If in the response data->status is set to true it means that the setting "Digital age of consent verification" in Administration > Plugins > Authentication >Manage authentication is set to "Yes" If in the response data->status is set to false, it means that the setting is set to "No" To be tested in Moodle 3.5 (master) Set the setting "Digital age of consent verification" in Administration > Plugins > Authentication >Manage authentication to "Yes" Execute the following command, replacing the Moodle URL with your own one. curl 'http://localhost/m/stable_master/lib/ajax/service.php?sesskey=pEz3ihR1lC' --data-binary ' [{"index":0,"methodname":"tool_mobile_get_public_config","args":{}}] ' | python -m "json.tool" Check that the fields: data->agedigitalconsentverification is set to true data->supportemail is set to the same value than the Moodle site (use the Site administration search and look for supportemail to check the value) data->supportname is set to the same value than the Moodle site (use the Site administration search and look for supportname to check the value)
    • Affected Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE, MOODLE_35_STABLE
    • Fixed Branches:
      MOODLE_33_STABLE, MOODLE_34_STABLE
    • Pull from Repository:
    • Pull Master Branch:
      MDL-61622-master

      Description

      For Moodle 3.3 and 3.4, we need to create a new WS for checking if age digital consent verification is enabled
      For Moodle 3.5 we should return the current configuration of the age digital consent in the tool_mobile_get_public_config

      The reason for creating a new Web Service for 3.3 and 3.4 is that we can't backport changes in Web Service signatures.

      The mobile app will check if it needs to use the WS function for 3.3 and 3.4 or can retrieve the information via tool_mobile_get_public_config (3.5 onwards)

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  19/Mar/18

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 hour
                  1h