We could create another, "resetpassword," table which forces a user to go to a reset password process upon first login. If the passwordresetneeded boolean is not cleared in postgres, then user is not able to visit other parts of the site.

Remaining To Do List on this Task:

Backend

Admin Validation Function:

✅ Implement a Golang validation function that verifies a user is an ADMIN before allowing them to perform the AddUser function.

• Also, ensure username validation within AddUser function to enforce lowercase, uppercase letters and numbers only.

Change Password Route:

✅ Create a /changepassword route in the server that handles password change requests.

Change Password Function:

Develop a ChangePassword function in Golang that:

✅ Validates the user's current session.
✅ Hashes the new password.
✅ Updates the user's password in the database.

Password Change Validation Function:

✅ Create a ChangePasswordNeeded validation function to check if the user needs to change their password.

✅ Ensure that secure actions such as create, trade, etc., cannot be undertaken until the user has changed their password.

Frontend

Update Routes for Secure Actions:

✅ Modify routes to restrict access to certain actions like /create, ensuring they are inaccessible if the user needs to change their password.

ChangePassword.jsx Layout:

Design and implement a ChangePassword.jsx layout that includes:

✅ An input field for the new password.
✅ Instructions or guidelines on creating a secure password.
✅ A button to submit the new password.

Modify Sidebar for Conditional Access

✅ Adjust the sidebar to show only the "Change Password" option if the user has the MustChangePassword flag set to true.
Redirection After Password Change:

✅ Set up redirection to the /profile page or another appropriate page once the password change is successfully completed.
UI Feedback for Actions:

✅ Implement user feedback mechanisms for both successful and unsuccessful password updates, such as notifications or alerts.

Testing and Validation:

✅ Thoroughly test the new password change feature to ensure it works seamlessly across different scenarios and handles edge cases properly.

Documentation:

• Update the system documentation to include information about the new password change requirement and its impact on user interaction with the system.