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

Don't prevent launch during migration claim failures

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 4.1.4, 4.2
    • LTI provider

      As reported by Mathieu Pelletier here: https://moodle.org/mod/forum/discuss.php?d=449264

      Essentially, we should probably just catch any exceptions generated during any attempted migration processing, and allow the 1.3 launch to continue without migration. We can't control how/why the platforms send this migration claim, and it may not always be possible to migrate. We need to skip it in such cases and remove the blocker to launches.

      Suddenly and without warning, however, I am now getting the following 
      mysterious error when a user tries to open the quiz from Canvas:
       
      2023/08/08
       15:52:58 [error] 3968442#3968442: *13312 FastCGI sent in stderr: "PHP 
      message: Default exception handler: Coding error detected, it must be 
      fixed by a programmer: Invalid 'oauth_consumer_key_sign' signature in 
      lti1p1 claim. Debug: 
      Error code: codingerror
      * line 95 of /enrol/lti/classes/local/ltiadvantage/entity/migration_claim.php: coding_exception thrown
      * line 246 of 
      /enrol/lti/classes/local/ltiadvantage/service/tool_launch_service.php: 
      call to 
      enrol_lti\local\ltiadvantage\entity\migration_claim->__construct()
      * line 341 of 
      /enrol/lti/classes/local/ltiadvantage/service/tool_launch_service.php: 
      call to 
      enrol_lti\local\ltiadvantage\service\tool_launch_service->migration_claim_from_launchdata()
      * line 125 of /enrol/lti/launch.php: call to enrol_lti\local\ltiadvantage\service\tool_launch_service->user_launches_tool()"  

            Unassigned Unassigned
            jaked Jake Dallimore
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

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