@schenedx Sorry for the delay! Here goes:
- What are you using ID Verification for? What is the business purpose?
We have a client using it to verify the student IDs, though that is done manually by the course staff.
- Are you using the same IDProbe backend or a different Verification provider?
No, we are using the manual verification overrides.
We use the views only to embed a page from a pluggable app, which presents a user verification form and stores data in a custom model. When a staff user “approves” the verification request, then a signal automatically adds a
ManualVerification model entry and bypasses the Software Secure requirement.
This was our way to avoid modifying the core, but it’s not the most elegant solution available: it needs the pluggable app + template overrides. The better option would be to have a generic ID verification model in the platform, and pluggability for multiple verification providers, as this would avoid having to rework the UI or do theme overrides.
We’re happy to open source our solution if there’s enough interest.
- If we deprecate this functionality on edx-platform, can you think of alternative method to verify learners?
If Open edX provides us hooks to intercept the enrollment process and trigger/redirect to user verification pages, then it’s fine to deprecate the feature.
Also, from my understanding, what you are deprecating here are the views, and not the entire verification functionality, right?
- If edx.org will no longer offer ID Verification functionality on edx-platform codebase, what you think is a solution to help the community make the transition?
The suggestion I’ve mentioned above works: having a generic verification models, with the ability to plug in custom verification providers (no complex mechanisms, a python package + configuration variable would work). The feature can be left disabled by default, and edx-platform doesn’t need any service-specific code in the core.