Skip to content
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

Add separate validation level for cellphone validation #63

Open
wens opened this issue Jun 15, 2019 · 1 comment
Open

Add separate validation level for cellphone validation #63

wens opened this issue Jun 15, 2019 · 1 comment

Comments

@wens
Copy link
Contributor

wens commented Jun 15, 2019

The plan is to do account validation with cell phone verification via SMS or AOTP solutions.
The solutions will almost all be using HTTP. Cell phone verification should be a separate level.

First, we need data fields to store the data. I suggest using the _unused1 field in struct userec_t for extra permissions. We might want to combine it with the existing userlevel into a 64bit unsigned value. For the phone number, the old _unused_phone field is still there.

Second, we'll need to duplicate the existing email validation system, but with separate storage for in-flight validation codes, as well as the central database used to check for duplicates.

Third, integration with service provider. Probably use libcurl, either in-process, or queued request in a separate daemon.

More to come later....

@chhsiao1981
Copy link
Contributor

2e1c6c6

(Is this issue already done?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants