...
| Attribute | Type | Required | purpose |
|---|---|---|---|
| name | string | true | name of user. can be combination of firstname , middle name and lastname |
| username | alphanumeric | truefalse | unique identity to identify user. user name will be unique per installation |
| password | alphanumeric | true | |
| phone | number | conditional | either phone or email is mandatory . but during creation time user can't pass both. |
| alphanumeric | conditional | either phone or email is mandatory . but during creation time user can't pass both. | |
| userType | string | internal | To identify user is Teacher or Other , as of now there is only two types |
| phoneVerified | boolean | internal | will be true only when user verified phone otp |
| emailVerified | boolean | internal | will be true only when user verified email otp |
...
Consumer (portal/app) can hold user data in local cache , and once OTP is verified then only they make create user api call.
| Pros | Cons |
|---|---|
|
|
Proposed solution 2:
User Data can be stored under sunbird as some temp table and once user verify OTP then , it will move data from temp table to different other places , from where they can used it.
| Pros | Cons |
|---|---|
|
|
Google sign In:
When user come to sunbird via Google sign in , Caller will do following check.
...