Project

General

Profile

Feature #1006

Updated by Vladimir Krisyuk over 6 years ago

h2. User should be able to submit the Register form and get an access to the App. 

 * On “Register” click, the form has to be validated (same as #1155    #1156 ) 
 * And In positive validation result the app. should search in the server for user with the combination of values of the fields: NPI, Key_code, Mobile phone, Email address. 
 * When user is mathched by values above, then the server should trigger the sms code to the user’s phone number and open the next screen “Sms verification”. 
 * Only after sms code submission the reqistration process will be completed and username/password will be created.  
 *And*    if there were already username/password - they have to be overwriten (TB) 

 *Negative flow1:* In case if user was not match in DB by fields: App. should show over the “Registration” screen an error message in the window: “The physician with the provided data was not found. Please try again or contact MDL account manager” 

 *Negative flow2:* If user was matched, but the key_code was expired in Db. Then show the error message on the “Registration” screen in the window: "The key_code you have provided is expired. Please request the new one."  

 *Negative flow3:* If user was matched, but the key_code was already used. Then show the error message: “The key_code was already used. User is already registered. Please recover username or password if you forget it” 

 *Negative flow4:* If user was matched, but his account is blocked (due 5 failure attempts for enter sms code) show the error message: “MDL Connect account is blocked. Please contact MDL support to unblock it.”  
 _Access can be blocked in #1007_ 


 for Devs: The 3rd party will be used for Two-factor authentication by the code. We need to choose one. 
 Example: https://rapidapi.com/blog/sms-apis-send-texts/ 
 https://www.nexmo.com/ 

 Mockups: 
 * 2.Registration 
 * 3.Sms verification 

Back