LTI Integration (Non-LMS)

1 Using Chromium Browser’s Renderer Engine
2 Consumer Platform Prerequisites
3 Get Data From Platform
- 3.1 LTI Parameters generated by SUMADI
4 Technical Workflow
5 User Experience Workflow
- 5.1 Faculty / Admin
- 5.2 Exam Taker (Candidate)
- 5.3 Testing the integration

Using Chromium Browser’s Renderer Engine

Taking advantage of the S2B’s renderer engine, Chromium (https://www.chromium.org), and programming interface, the browser can collect key HTML object identifiers which trigger the desired workflow when supporting non-LMS platforms.

Figure 1- Understanding the Architecture of Web Browsers

Leveraging the web browser’s render tree, these observability and monitoring allows the securing of the navigation and enabling of invigilation features without the systems exchanging messages or data.

Figure 2- Rendering engine basic Flow

Sumadi Secure Web Browser is based on the Electron project. This gives deep control on bridging main process and rendering process that enables hooking Sumadi workers and workflow based on navigation data and DOM Elements provided by the platforms stie.

Consumer Platform Prerequisites

The following list or prerequisites is necessary for the SUMADI team to begin the analysis, development, testing, and quality assurance of the online exam engine that requires to add security and integrity.

SUMADI:

Account registration.
LTI parameters and institution id per environment (DEV, STAGE, & PRODUCTION) as defined and required.

Consumer platform (Online Assessment Platform):

Faculty and Student users for development, testing, and Quality Assurance
Access to DEV environment (non-production) for development and testing
Access to STAGE environment (non-production) for quality assurance and User Acceptance Testing
Key documentation for setting up users and exams in the consumer platform.

Get Data From Platform

SUMADI gathers information about the user (username, role), course name, assessment name, platform URLs for the intended services to be launched.

LTI Parameters generated by SUMADI

This is an example of a POST requests that SUMADI generates, SUMADI gets the user context in the testing platform. the following parameters list details the data values passed as part of the LTI launch. A test environment (e.g., https://test.sumdai.net/lti/v1) will require the following body parameters as follows:

Parameter Name	Default Value	Comments
Required parameters based on LTI Standards:
`lti_message_type`	basic-lti-launch-request
`lti_version`	LTI-1p0
`resource_link_id`		Set an opaque unique identifier that the Tool Consumer guarantees will be unique within the Tool Consumer for every placement of the link
Other parameters
`user_id`		User ID or other identifying data
`lis_person_name_given`		User’s `first name` in the LMS.
`lis_person_name_family`		User’s `last name` in the LMS.
`launch_presentation_return_url`		The return URL after going through the SUMADI authentication process. This should be the URL for the exam start landing page
`tool_consumer_info_product_family_code`		An ID you must establish to identify the LMS
Security parameters
`oauth_consumer_key`		Set a proper key and secret and share with us the oauth credentials
`oauth_signature_method`	HMAC-SHA1
`oauth_timestamp`
`oauth_nonce`	‘’
`oauth_version`	1.0
`oauth_signature`
`oauth_callback`	'about:blank'
Custom parameters
`custom_account_id`		Unique client ID. This ID will be provided by the SUMADI team
`custom_user_locale`		Value that determines the language in which the SUMADI platform will be presented: en/es/pt (are currently supported.)
`custom_user_role`		The role inside the LMS context for the user.
`custom_course_name`		Name of the course where the LTI is being launched
`custom_course_id`		The unique ID for the course where the LTI is being launched

Technical Workflow

Overall, the workflow is as follows.

Depending on the customer platform and online exam engine’s web framework, design, CSS, HTML, and scripting, this may require a different or alternate workflow. This is determined in the analysis phase where SUMADI engineers test the different users provided and environments to understand the flow, determine a feasible trigger, and launch the expected workflow.

Essentially, triggers launch the workflow, which redirects test takers to SUMADI for registration and verification using the Wizard, and then redirected back to their exam with fully invigilated features enabled and actively monitoring their exams.

User Experience Workflow

SUMADI recommends two scenarios to review evidence for online proctoring already delivered and reports:

License the Record and Review application. This is the most straightforward process and allows institutions to analyze reports and export evidence for any actions or purposes required (see more detail here).
Require faculty, proctors, or reviewers to download the Sumadi Secure Browser (S2B) to allow them to enter and review reports without requiring any additional web platforms.

The 2nd option is detailed below.

Faculty / Admin

The user clicks an administrator panel option for entering SUMADI.
The LTI launch is sent towards the SUMADI platform along with all the required fields specified above.

SUMADI registers the user if the user is new within the platform automatically.
SUMADI registers the course if there wasn’t any previous record of it within the system.
SUMADI registers the assessment if there wasn’t any previous record of it within the system.

The user explores proctoring Reports.

Exam Taker (Candidate)

The LTI launch is sent towards the SUMADI platform along with all the required fields specified above.

SUMADI registers the test taker if the test taker is new within the platform automatically.
SUMADI registers the course if there wasn’t any previous record of it within the system.
SUMADI registers the assessment if there wasn’t any previous record of it within the system.

The test taker will be redirected to the proctored exam list.

Testing the integration

During testing, the Sumadi team will provide a development build for the Sumadi Secure Browser (S2B).
Upon first install, set the provided Institution ID (identifier provided by Sumadi).
Navigate to the desired course, exam, and LTI tool link.
The student starts a SUMADI proctored exam.

An LTI launch is executed towards the SUMADI platform with all required parameters and with the additional SUMADI Ids that are sent when activating an assessment as proctored:

sumadi_assessment_id: Unique assessment ID within the SUMADI platform.
sumadi_course_id: Unique course ID within the SUMADI platform.

The user goes through the authentication process.

Registration (For new users within SUMADI)
Authentication.
The user is redirected towards the exam start page.
The user starts the exam.
The user pauses the exam. (IF ENABLED)
The user finishes the exam.

Works Cited

Services, A. W. (2023). What is an API (Application Programming Interface)? Retrieved from Amazon Web Services: What is an API? - Application Programming Interface Explained - AWS .

Unadkat, J. (2023, 04 27). Understanding the Role of Rendering Engine in Browsers. Retrieved from BrowserStack: Understanding Role of Rendering Engines in Browsers | BrowserStack

SUMADI Live AI Documentation