Add Extensibility Mechanisms to IDV to Enable Integration of New IDV Vendor Persona

Abstract

The goal of this initiative is to fix a pain point. 2U would like to replace the IDV vendor it uses. Our solution is to leverage existing and add new necessary extensibility mechanisms to support a 2U-specific integration with a new IDV vendor, Persona. This will require changes to the platform to enable this integration, but we're seeking guidance on how best to do this. Our integration with Persona may need fewer extensibility mechanisms than would be necessary for an Open edX operator to integrate another IDV vendor, because 2U uses IDV to a lesser extent than is supported by the platform and because we are moving photo collection off platform.

We would like to start with posing a series of questions that will help us understand how to design our approach. These questions are listed on the linked proposal. Once we have a better understanding of the community and platform needs, we can put forth a more concrete proposal.

Detailed Product Proposal

https://openedx.atlassian.net/wiki/spaces/OEPM/pages/4307386369/Proposal+Add+Extensibility+Mechanisms+to+IDV+to+Enable+Integration+of+New+IDV+Vendor+Persona

Context & Background (in brief, if a Product Proposal is linked above)

The platform supports a custom integration with Software Secure for an IDV feature. 2U would like to replace the IDV vendor it uses for IDV with Persona. 2U uses IDV only for the Name Affirmation feature, which is a feature that requires a certificate-bearing learner to perform IDV when they change their profile name or verified name in specific ways. 2U does not use IDV to block certificate generation nor does 2U require IDV as part of the upgrade process. Open edX operators may choose to enable blocking certificates on IDV via a Django setting, and they may choose to disable the Name Affirmation feature. It is unclear to 2U how IDV is used by the community and what features or integrations are necessary to support an extensible approach. It is also unclear to 2U how to add the extensibility points it needs to enable this integration if those changes are not part of a larger "make IDV pluggable" initiative.

Scope & Approach (in brief, if a Product Proposal is linked above)

We are too early in the process to answer this question. We will address this as we get closer to a design.

Value & Impact (in brief, if a Product Proposal is linked above)

We are too early in the process to answer this question. We will address this as we get closer to a design.

Milestones and/or Epics

We are too early in the process to answer this question. We will address this as we get closer to a design.

Named Release

Timeline (in brief, if a Product Proposal is linked above)

This project is high priority and will be started as soon as possible. We would target the S named release.

Proposed By

Additional Info

Proposal

openedx / platform-roadmap