Opened 7 years ago
Closed 5 years ago
#10 closed defect (wontfix)
Trac account manager plugin password reset functionality does not work
| Reported by: | pat | Owned by: | pat |
|---|---|---|---|
| Priority: | major | Component: | ticket-system |
| Keywords: | Cc: |
Description
When an admin requests a password reset for a user, a new temporary password is generated and sent to the user, but the user is not able to use that temporary password to log in.
The temporary password is supposed to be stored in the ResetPwStore? (which I think is a table in trac.db), which is supposed to be consulted as a fallback if authentication using other authentication methods fails. However, from all appearances, either the temporary password is not being put into the ResetPwStore?, or the ResetPwStore? is not being consulted - I can't tell exactly which, and nothing I can see in the log (even when it's set at DEBUG level) appears to shed any light on the problem.
The problem manifests in a similar way to what's reported here:
https://trac-hacks.org/ticket/11869
though I do not know if our problem is the same.
As a workaround, the Trac administrator can manually set a new password in the "Admin -> Users" menu using the account manager plugin, filling in the user's username and desired new password in the user form and hitting "Change" (to change an existing user). In our configuration, the user would then be forced to change their password (again) on their next login.
Change History (2)
comment:1 Changed 7 years ago by pat
- Owner changed from admin to pat
- Status changed from new to accepted
comment:2 Changed 5 years ago by pat
- Resolution set to wontfix
- Status changed from accepted to closed
The underlying issue in the account manager plugin (ticket 11869 in trac-hacks.org) appears to have been fixed some time ago. We could probably correct this issue by upgrading, but the risk/reward ratio of trying to do that right now is probably too high, particularly since this ticket has been open for 3 years and I seem to be the only one who's noticed the issue.
I'll close this as "wontfix", it seems unlikely we'll be taking any action on this.