Project

General

Profile

Actions

Feature #1451

closed

Feature #1002: Feature - User access to the app.

Feature #1011: Req. - Forgot password / username

Req. - Forgot password / username - back-end part

Added by Olga Bakhmat almost 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Alice Gor
Category:
-
Target version:
-
Start date:
02/10/2020
Due date:
% Done:

100%


Subtasks 2 (0 open2 closed)

Bug #1612: Invalid user credential >> Appropriate Error Message to be display instead of BAD REQUESTClosedAlice Gor02/10/2020

Actions
Bug #1635: Forgot User name : when Provider is given as email> No email is recievedClosedAlice Gor02/12/2020

Actions
Actions #1

Updated by Olga Bakhmat almost 6 years ago

  • Status changed from New issue to Needs Testing
  • % Done changed from 0 to 100
Actions #2

Updated by Artem Bakhmat almost 6 years ago

Summary: new endpoints were implemented:
1) Forget password:
POST /api/mdlaccount/forgetPassword
Request parameters:
  • username
Rule:
  • if user is not found then message "User is not exists" is returned
  • If user is exists with specified username then sms is send to telephone number with temp token - "Enter reset password code {code}"

After user get security code then he should verified it by using api POST /api/mdlaccount/verifyResetPasswordCode

2) Forget username:
POST /api/mdlaccount/forgetUsername
Request parameters:
  • email
  • provider (0 - email, 1 -Sms)
Rule:
  • if email is null or empty - then validation message "Email was not provided" is returned.
  • if user with specified email is not exists then message "User with such email is not found. Please contact support."
  • if user found then based on the provider value email or sms is send to user with next text body "Your username is {user.UserName}".

Please refer to https://develop_feature_ironjab-api.gbglis.xyz/swagger/index.html for testing and checking request/response data parameters.

Actions #3

Updated by Artem Bakhmat almost 6 years ago

  • Assignee changed from Artem Bakhmat to Alice Gor
Actions #4

Updated by Alice Gor almost 6 years ago

The API is tested and verified in DEV

Actions #5

Updated by Alice Gor almost 6 years ago

  • Status changed from Needs Testing to Closed
Actions #6

Updated by Alice Gor almost 6 years ago

  • Status changed from Closed to In Progress
Actions #7

Updated by Artem Bakhmat almost 6 years ago

Update: when user select "Email" option for getting email with username then server will do next:

1) Creates record in the tblemails table with related column values:
- Txt_Subject = "Username"
- Txt_Message = "Your username is {username}"
- Txt_From = ""
- Txt_To = "{email}"
See screen - http://prntscr.com/r2dqwg
Example of DB query: select * from tblemails where Txt_Status <> 'Sent' and Txt_To = '';

2) Then global service that process pending emails is sending email to recepients.

For testing purpose there enough to check creation of record in the tblemails table, because email sender might be disabled on test environment.
Please test and let me know if you have any questions

Actions #8

Updated by Alice Gor over 5 years ago

  • Status changed from In Progress to Closed

The APi is tested and verified in DEV

Actions

Also available in: Atom PDF