Uploaded image for project: 'Moodle app'
  1. Moodle app
  2. MOBILE-2252

LTI External Activity start reuses nonce

    XMLWordPrintable

    Details

    • Testing Instructions:
      Hide
      1. Via the Mobile app open this activity: https://mobile34.next.moodle.com/mod/lti/view.php?id=79
      2. Check that in the new page opened, the oauth_nonce value is different every time you do a request in the mobile app via click the "Launch activity" button or clicking the quick link button in the section view.
      Show
      Via the Mobile app open this activity: https://mobile34.next.moodle.com/mod/lti/view.php?id=79 Check that in the new page opened, the oauth_nonce value is different every time you do a request in the mobile app via click the "Launch activity" button or clicking the quick link button in the section view.
    • Affected Branches:
      MOODLE_34_STABLE
    • Fixed Branches:
      MOODLE_34_STABLE
    • Sprint:
      Moodle Mobile 3.4.1

      Description

      1. Start an external activity 
      2. Click 'Launch the activity'
      3. Click 'Done' to close the window
      4. Click 'Launch the activity' again
      5. Result: activity doesn't start, but gives an error

      When checking the logs from the LTI app, I noticed that the timestamp/nonce pair is reused.

      I also tried to go up to the course first to open the activity again, but the same problem appears. Even quitting the app doesn't work.

      The link works again after 5 minutes. (cache issue perhaps?)

        Attachments

          Activity

            People

            Assignee:
            jleyva Juan Leyva
            Reporter:
            remko_troncon Remko Tronçon
            Peer reviewer:
            Dani Palou
            Integrator:
            Juan Leyva
            Tester:
            Juan Leyva
            Participants:
            Component watchers:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Fix Release Date:
              28/Feb/18