This behavior has been resolved and deployed to the production environment as of 7/17/24.
Description
When users first access an external tool which generates a token on behalf of the user with the OAuth2 flow from within New Quizzes (e.g. in the RCE in NQ) users receive an <domain>.instructure.com refused to connect. error and are unable to authorize the tool. If the user has already authorized the tool while in Canvas they are able to access the tool in New Quizzes successfully.
Expected Behavior
Instead users should be able to authorize external tools to generate a token on their behalf from within New Quizzes.
Workaround
Authorize the tool in Canvas first (e.g. in the RCE while editing a page) then use the tool in New Quizzes
Steps to Reproduce
Prerequisites: A course with a New Quizzes quiz and a teacher enrolled.
-
As the teacher launch Commons from the global navigation menu to bring up the OAuth authorization screen but do not click Authorize (for some reason you need to do this to get Commons to bring up the authorize screen in New Quizzes, but in the example the admin brought up they were just using the normal workflow with their external tool)
-
Go to the quiz, open the RCE for the quiz instructions, and select Commons Favorites from the Apps menu icon. Note that the sidebar where the Commons Favorites should show displays a <domain>.instructure.com refused to connect. error with an Refused to frame 'https://<domain>.instructure.com/' error in the console.
Additional Info
INTEROP-8625
Known issues indicate notable behaviors that have been escalated to the Canvas engineering team. Known issues are not a guarantee for an immediate resolution. This document is for informational purposes only and does not replace the Support process. If you are encountering the behavior outlined in this document, please ensure you have submitted a Support case (per your institution's escalation process) so Canvas Support can adequately gauge the overall customer impact and prioritize appropriately.
