Subscribe to receive emails everytime Atomic Assessments US publishes an update.
By subscribing to status updates you agree to Privacy policy and Terms of Service.
Instructure issued a new Canvas developer key to Atomic Jolt and disabled the old one. They automatically enabled the new key for all customers that had enabled the previous Atomic Jolt developer key. The new Developer Key is named the same as the old one (Atomic Jolt App Installer).
Instructure did this in response to observing anomalies in network traffic. The anomalous traffic appears to have been more widespread than just Atomic Jolt’s Canvas developer key because Instructure disabled dozens of vendor Canvas developer keys.
Impact. Customers that used Atomic Assessments products in Canvas experienced degraded functionality. Our research shows that the impacts were as follows:
All aspects of the student experience continued to function as expected.
Teachers and admins were unable to use the applications.
Time frame of impact. Impact started when Instructure disabled Atomic Jolt’s API key at approximately 2:30am Mountain. They were resolved at approximately 10:00am Mountain when the Atomic Jolt applications were updated to use the new Canvas developer key issued by Instructure.
Resolution. We’ve updated the Atomic Jolt applications to use the Canvas new developer key. This will allow the applications to obtain new Canvas API tokens through an OAuth process.
Re-authorizing Atomic Assessments. When teachers using Atomic Assessments access the tool the first time Canvas will ask the teacher to authorize the tool. It will only ask them to do that once.
In addition, in order for LTI 1.1 installs of Atomic Assessments to automatically copy content when courses are copied a Canvas root admin will need to authorize the application. LTI 1.3 installs will not require an administrator to authorize the application.