-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DEPR]: Software Secure IDV Integration #35128
Labels
depr
Proposal for deprecation & removal per OEP-21
Comments
MichaelRoytman
changed the title
[DEPR]: Software Secure IDV Integration
[DRAFT][DEPR]: Software Secure IDV Integration
Jul 17, 2024
MichaelRoytman
changed the title
[DRAFT][DEPR]: Software Secure IDV Integration
[DEPR]: Software Secure IDV Integration
Jul 17, 2024
This was referenced Sep 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Proposal Date
2024-07-17
Target Ticket Acceptance Date
2024-07-31
Earliest Open edX Named Release Without This Functionality
Sumac - 2024-10
Rationale
The verify_student Django app in the edx-platform implements various forms of identity verification (IDV) that are used across the platform. One implementation of IDV is an integration with Software Secure, an IDV vendor. To our knowledge, edx.org is the primary user of this integration. Until recently, we were aware of only two Open edX users of this integration - EDUlib and Open Craft - and we have since learned that they no longer use it. 2U is replacing Software Secure as its photo IDV vendor. For this reason, the Software Secure integration will be unused and has no purpose in the core. It is dead code and contributes to the unnecessary complexity of this application.
Removal
The implementation of the Software Secure integration has its tentacles in a few areas of the platform. This may not be an exhaustive list, but it should be comprehensive.
Replacement
We do not propose replacing the Software Secure IDV integration because it is not appropriate to add integrations with specific IDV vendors into the core.
2U is in the process of proposing adding extensibility mechanisms to the verify_student application to enable the seamless integration of additional IDV vendors into Open edX installations without polluting the core. This is not a replacement per se, but it will provide the capability for Open edX operators to integrate with IDV vendors of their choosing. Please see openedx/platform-roadmap#367 for more details.
Deprecation
We do not believe marking code for deprecation is necessary given the low usage of Software Secure IDV.
Migration
This is TBD, pending the outcome of openedx/platform-roadmap#367. Assuming that that proposal is approved, migration will be necessary to do the following.
VerificationAttempt
model.VerificationStatus
model based on the above migration.In order to update the VerifiedName model, the following may be a reasonable approach for migration.
verification_attempt
to the VerifiedName model, which will be aForeignKeyField
toVerificationAttempt
. In the beginning, a given VerifiedName will have a value for eitherverification_attempt_id
(via SoftwareSecurePhotoVerification) orverification_attempt
(viaVerificationAttempt
).VerificationAttempt
model, we will also set theverification_attempt
field to the proper reference associated with the newVerificationAttempt
instance. If a VerifiedName has values for both fields,verification_attempt
will take priority.VerifiedName.verification_attempt_id column
will be removed.VerifiedName.verification_attempt_id
column will be dropped.Additional Info
Task List
TBD
The text was updated successfully, but these errors were encountered: