Proctoring process based on the proctoring backend

[jmakowski1123]

Opportunity Objective Proctoring pluggable backends were introduced in the Hawthorn OeX release. That gave a possibility for simple integration between OeX and different proctoring services from the market.

At the same time, OeX is still highly focused on certain proctoring flows which could not be supported or such support could be complicated by the proctoring services with different flows among them: pre-requisites:

• ID verification
• a certain range of the enrollment modes
• there are several ways to bypass ID verification, nevertheless it doesn't depend on proctoring backend and could require additional admin/development work;
• default proctoring templates also depend on the preferred proctoring flow and should be updated with adding different proctoring backend.

Market Evidence There is a bunch of new proctoring services on the market, which would like to have a simple integration with the OeX. We in RaccoonGang have a lot of requests for helping to end integration with the proctoring plugin simply added to the platform, but doesn't work as expected because of plenty of explicit requirements and pre-requisites.

Proposal Specifics Since the proctoring service start work on splitting into two parts: backend API level and frontend based on MFE it seems a great time to enhancements into the integration process between OeX and proctoring plugins. For the very beginning, several initial points could be specified:

• add flexibility to the proctoring pre-requisite depends on the plugin flow and/or organization requirements
• make the proctoring frontend be oriented on the plugin proctoring flow

Success Measures The organization's admin will have a tool for a simple plugin integration and proctoring flow configuration on the platform. Proctoring flow and pre-requisites would be based on the plugin and easily adjustable which makes the integration process straightforward and clear.

Students and instructors won't be confused by misconfiguring frontend when the plugin's proctoring flow is different from the default one.

[Source: https://openedx.atlassian.net/browse/OEROADMAP-47]

[jmakowski1123]

Next step: Discovery around whether native capability is necessary.