I would prioritize getting REST endpoints working for the workflow – i.e. at a minimum:
email property on user resource can be set and retrieved with appropriate permissions (I’d assume getting user email addresses except for the current user might take additional privilege beyond simply Get Users)
Client can POST a password reset request and the response is the same whether or not username or email address exists (i.e., to avoid exposing existence of usernames or email addresses to anonymous requests)
Client can POST a password reset token to password reset request and to validate it (so application can tell if user’s token is valid)
Client can POST a valid password reset token along with new password to change the user’s password.
Front-end use of the API and even sending email messages could be added later as long as the REST endpoints exist. If the REST endpoints aren’t complete (part of core) by the end of GSoC, then it will be far more work for someone to pick up where you have left off.
Could you edit your original post to include relevant links (links to your project’s wiki page and relevant code repository or branch)?
Thank you @harisu for the presentation, good work so far! I hope everything that @burke mentioned is clear to you, and can you please share the link to branch in the git repository?
@burke Thanks very much for those points i really appreciate it i will commence with addressing those immediately i finished with the pending pull request and it’s merged.