...
| Attribute | Type | Required | purpose |
|---|---|---|---|
| name | string | true | name of user. can be combination of firstname , middle name and lastname |
| username | alphanumeric | true | 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 |
| signUpType | string | internal | To identify user came via selfsignUp, googleplus , statelogin or stateonboard |
| phoneVerified | boolean | internal | will be true only when user verified phone otp |
| emailVerified | boolean | internal | will be true only when user verified email otp |
Self sign up work flow:
- User will enter all mandatory field (name, phone/email, username,password) on consumer portal/app
- Consumer will make call for generate OPT for either phone or email
- OTP Generation will be taken care by Design for One time password (OTP)
- Once User enter OTP, consumer will check OTP basic Validation and then it will call create user APi:
- System will check uniqueness of email/phone , username and OTP , if every thing is ok then it will create user under sunbird.
- if any validation fails then it will throw proper error
...
- What should be userName in this case?
- Does system need to generate password for Google signup user?
- Do we need to send any welcome email to user? if yes then what should be content?
- What will happen if some old Google user won't have firstName or name itself?
- There might be scenario user already exist but his status is deleted?
- Do we need to carry loginId as well?
- In Old implementation during user create we have to send phoneVerified as true?