| Summary: | Can't change password | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Michael Golubev <borlander> | ||||
| Component: | Accounts.eclipse.org | Assignee: | Eclipse Webmaster <webmaster> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P2 | CC: | chris.guindon, webmaster | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Michael Golubev
Created attachment 268306 [details]
Login page screenshot with "...Try new password.. " message
Furthermore, I just found a couple of emails in my mail box, like this one: Dear Michael Golubev, The password of your eclipse.org account has been successfully updated on Fri, 2017-05-12 04:30 from [XXX.XXX.XXX.XXX]. Still, only the old password actually works, and not the updated one (In reply to Michael Golubev from comment #0) > I had been required to change my Eclipse password (by "Your password will > expire in X days" emails from Eclipse. > > But when I am actually trying to update one (at > https://accounts.eclipse.org/user/73844/edit Account Settings tab), after > pressing Save, I am being redirected to the Login page like the attached > screenshot. We automatically logout users after they submit a password change request. > > The login page shows "Password change has been submitted... Please try to > login with new password" message. However the new password does not work, > while the old one which is about to expire does work at both Login Page or > at the Bugzilla login, which allowed me to submit this bug. I can confirm that this is an issue when using the "Forget my password" page and when the user tries to update his password on the Edit my profile page. I am upping the priority for this bug. After our investigation on Friday, we were able to detect a problem with our LDAP configuration. Assigning to webmaster. A timeout for idle connections had been added, and that had the side effect of killing the connection that the reset/change process relied on. We've removed it. -M. |