Closed sergei-maertens closed 1 month ago
My notes from the estimate:
uitbreiden email component met optie requireVerification
(types, builder) in
validatie tab
backend: add model openforms.formio.models.EmailVerificationCode
. Fields:
Generates a 6-char verification code on creation, exclude confusing characters. Doesn't have to be unique.
backend: add template for sending the verification code
backend: add endpoint to request verification code
EmailVerificationCode
, render template and send
emailbackend: add endpoint to verify code
verified
flag to TrueSDK: when email component requires verification, add a button "Verify".
SDK: clicking button open modal to enter code. Upon opening of modal, fire API request for a code verification creation. Show message when that is completed & render text input to enter code
SDK: submitting code in modal calls endpoint to verify & report feedback (errors, success)
Backend validation: if verification is required, check that the email is still the same (you can change the input after getting the verification code) & that the email was indeed verified, otherwise return validation error saying that verification is required
Refinement: transition from formio component/template to React button/modal is going to be a challenge.
Taiga DH 684, business case "WMV", needs to be added to intranet still
To address mistakes in provided email addresses, we need to add an (optional) email verification flow for forms where the email address is crucial. The goals are:
The verification process happens during the form filling, not after the form is submitted (different from typical user signup flows).
User interaction
myname@example.com
Imlementation
requireVerification
(can go in thevalidation
nest obj I suppose)