Browser workflow

The workflow between the integration components looks as follows:

1. A user loads the page where proctoring is required.
2. The LMS generates a special JWT (JSON Web Token) with encrypted data inside.
3. The SDK receives the exam parameters from the Proctor Server (serverOrigin).
4. The SDK displays a modal pop-up window with the exam preparation steps, such as system check, submission of identification photos, screen and microphone sharing, and acceptance of the exam rules.
5. After the user successfully completes the preparation steps, the exam session is initiated.
6. The SDK triggers a special event indicating the start of the exam. The event can be intercepted using a callback function.
7. The modal pop-up window is replaced with the user interface panel.
8. The user can then proceed with taking the exam.
9. When the SDK receives a signal from the proctoring server indicating the end of the session, it stops recording the video.
10. The SDK triggers a special event indicating the end of the exam. The event can be intercepted using a callback function.
11. The SDK uploads the remaining video files in the queue to the server and issues a special event indicating that the files have been uploaded.
12. After the video files are uploaded, the exam scoring is calculated.
13. The scoring results are passed to the LMS through an API call.