code Issue: password field not required for forgot password feature

[varshahindupur09]

Expected Behavior: The forget password is a feature where a user need not provide their own passwords to reset their password.

Current Behavior: The forget password API takes password as an input and username instead of just email.

Possible Solution: Generate OTP and share that on email when user wants to reset their password and remove the password field as a required field.

Steps to Reproduce: As shown in the image, add the username of the password and the password for that user.

Context (Environment): Forget Password API

Detailed Description: This is a feature that would allow us to work on resetting the password in case user has forgotten these credentials.

Possible Implementation: As shared on possible solution, you can also share the resetting password link instead of OTP generation.

[dubeydivya14]

Thanks for bringing up this issue.

It seems you're suggesting that the 'Forget Password' feature should not require the user to provide their current password, but instead release an OTP or resetting password link via email, which indeed makes more sense.

Here is the plan:

1. I will create a new branch 'fix_forget_password' to isolate this change.
2. Update the 'Forget password' API, making the 'password' field optional.
3. Implement the feature to generate an OTP or to create a password reset link, which will be sent to the registered email address associated.
4. Amend the existing tests to accommodate this change, as well as adding new tests to ensure correct function of the feature.

I will aim to address this issue in the next sprint. Once I've committed the change and tested it, I will update you here.

If you have any other suggestions related to the above plan or anything else, please let me know.

---

This response was generated by AI-GitHub-Interlocutor and may not be accurate or appropriate. The author of this repository and the creator of the AI model assume no responsibility or liability for any consequences arising from the use of the information provided in this response. 🤖

[dubeydivya14]

Comment:

Thank you for bringing up this issue.

It seems you're suggesting that the 'Forgot Password' feature should not require the user to provide their current password, but instead either generate an OTP or create a password reset link, which will be sent to their registered email. This indeed makes more sense and improves the user experience.

Here are the steps we're planning to take based on your suggestion:

1. Create a new branch 'fix_forgot_password' to work on this issue.
2. Update the 'Forgot password' API endpoint such that it only requires the user's email, and no longer their current password.
3. Implement either the OTP feature or password reset link, which will be sent to the user's registered email.
4. Update the existing tests to cater for this change, and add new tests to validate the new implementation.

We hope to address this in our next sprint. Once we make the change and test it thoroughly, we'll update this issue.

Please let us know if you have any further suggestions or feedback!

---

AI-GitHub-Issue-Helper is an automated service. For any issues, contact the repository owner.

---

This response was generated by AI-GitHub-Interlocutor and may not be accurate or appropriate. The author of this repository and the creator of the AI model assume no responsibility or liability for any consequences arising from the use of the information provided in this response. 🤖

[dubeydivya14]

Thank you for bringing this issue to our notice. You're absolutely right. The "Forgot Password" feature should not require the current password but should rather send an OTP or a password reset link to the registered email address. This is a better and more secure approach to handle forgotten passwords.

Here's how we plan to address this:

1. Create a new branch named 'fix_forgot_password' specifically for this issue.
2. Update the 'Forgot Password' API to remove the password field and replace it with an email field.
3. Implement the generation of OTPs or password reset links, which will be sent to the user's email address.
4. Update relevant tests to reflect this change and add new tests to ensure the updated feature behaves as expected.

This change will be scheduled for our upcoming sprint. Upon completion and thorough testing, we'll update this issue thread.

Do not hesitate to share if you have more questions or suggestions we should take into consideration!

Please note that this is a automatically generated response by AI-GitHub-Issue-Helper.

---

*This response was generated with the help of AI tool and may not be accurate or appropriate. The author of this repository and the creator of the AI model assume no responsibility or liability for any consequences arising from the use of the information provided in this response.

[dubeydivya14]

Thank you for reporting this issue.

Indeed, the password field should not be required when a user is trying to reset forgotten credentials. Using an OTP or a password reset link sent via email enhances the user experience and also adds an extra layer of security.

Let's proceed with the following steps to resolve this:

1. Create a dedicated branch 'fix_forgot_password' to isolate these changes.
2. Amend the 'Forgot password' API to eliminate the need for the current password. The only required information should be the user's email address.
3. Include the functionality to generate OTPs or password reset links that will be dispatched to the user's registered email.
4. Modify existing tests and add new ones that will verify the new functionality.

We aim to address this problem in the forthcoming sprint. Once we have made the necessary changes and conducted adequate testing, we will provide an update here.

If you have more suggestions or queries about this plan, please let me know.

---

AI-GitHub-Issue-Helper is an automated service developed to help with GitHub issue tracking. If you have any concerns, please reach out to the repository owner.

---

Note: This response was generated by an AI tool and may not be entirely accurate or suitable. The author of this repository and the creator of the AI model assume no responsibility or liability for any consequences arising out of using the provided information.

---

*This response was generated with the help of AI tool and may not be accurate or appropriate. The author of this repository and the creator of the AI model assume no responsibility or liability for any consequences arising from the use of the information provided in this response.