Engineers are currently investigating the issue.
Summary:
When a user attempts to launch a quiz using {{Respondus Lockdown Browser}} (LDB), the launch sequence may take long enough for the initial session to expire.
Expected Behavior:
Users should be able to launch quizzes using LDB without the session timing out directly after startup
Steps to Reproduce:
Prerequisites: a course with {{Respondus Lockdown Browser}} setup, containing a New Quiz set to use LDB, and a student, who has LDB installed
- As the Student, launch LDB from the quiz
- Notice the startup and initialization may take long enough for the session to expire
Additional Notes:
- This seems to happen more often for a user’s first launch of the quiz using LDB
- This is further exacerbated by:
- The first-time launch of the newly installed LDB, due to the permissions and initial setup
- LDB’s popup prompting you to close background windows, due to the time it takes to read said popup, especially for slower readers
- Launch a second application, e.g. Slack
- As the Student, launch LDB from the quiz
- After startup, read through the popup at a normal/careful pace
- Notice that this may take long enough for the session to expire
- From partnerships who reached out to Respondus support:
- Respondus Support noted that this behavior is primarily a side effect of the Rosetta emulator on macOS. The first launch of any program running under Rosetta after a reboot experiences a significant delay. Because this initial launch routinely exceeds 60 seconds, the Canvas reauth token expires before the browser fully connects. Respondus has requested evaluating whether the lifespan of this launch token/timeout can be extended beyond 60 seconds on the Canvas side to accommodate this behavior.
