1
Canvas
Identifies the user, role, course, tenant, and assessment.
SEB Canvas LTI
One connected workflow
The integration does not replace Canvas or Safe Exam Browser. It makes their handoff manageable for the people running assessments.
1
Identifies the user, role, course, tenant, and assessment.
2
Applies policy, issues the SEB configuration, and verifies the current proof.
3
Enforces the approved kiosk, navigation, tool, and exit settings on the device.
Evaluator questions
These are the practical differences between deploying SEB alone and connecting it to an institution-wide Canvas workflow.
It gives instructors a course-level management view, students a launch path on the assessment page, and root-account administrators an operational dashboard.
Safe Online Exam validates the signed LTI launch and uses the verified user, course, role, tenant, and deployment for every protected workflow.
The assessment page opens a short-lived SEB configuration. After current Config Key proof succeeds, the service obtains a Canvas session handoff without copying the student's browser cookies.
The institution configures an LTI 1.3 Developer Key, a Canvas API OAuth Developer Key, the account-level app installation, and a small account-theme detector script.
Review the architecture, deployment choices, data boundaries, and license.
Technical overviewFollow the operator path from prerequisites through Canvas registration and verification.
Setup overviewExamine signed launches, proof, custody, limits, and short-lived state.
Security detailsA demo follows the full path from instructor configuration through the student assessment launch.