Closed Bug 459520 Opened 17 years ago Closed 17 years ago

freshly-reset passwords often don't work on the passwordreset page

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pascalc, Assigned: oremj)

Details

Guillermo Movia's LDAP password was never communicated to him (see bug #404903), please reset it and send him : guillermo.movia@gmail.com thanks
--> Server Operations, as this is an IT issue
Assignee: marcia → server-ops
Component: Account Request: SVN → Server Operations
QA Contact: svn-acct-req → mrz
Password reset has been initiated. He should have an email with instructions for completing the password reset.
Assignee: server-ops → justdave
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Yes, I had the email and change my password. But now i have this problem: the system to change the password accept the «¡» (opening exclamation mark) but the web services don't accep it. I couldn't log in again to reset the password now. Thanks
reopening, the password Guillermo provided does not allow him to connect to web apps that use LDAP authentification, including the password resetting web app. His password should be reset again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Which web services don't allow it? Those would be what we need to fix probably.
Assignee: justdave → server-ops
Dave, like i wrote in #3, i couldn't use any services. I suppose that the problem is that i use a non-aschii character (Verbatim login says something about it).
But everything we have is supposed to allow that stuff. So Verbatim is one of them...
This is the error i have in Verbatim login: UnicodeEncodeError: 'ascii' codec can't encode character u'\xa1' in position 3: ordinal not in range(128) In the other services (like in th resettng web app) it continue to ask me for the user and password
I found this for the Verbatim error. I suppose that this answer is only valid for Verbatim, that use Python, but maybe it's something similar with the other web services. http://trac.edgewall.org/wiki/UnicodeEncodeError
Looks like justdave was working on this.
Assignee: server-ops → justdave
No, I wasn't. This is either Aravind or Oremj because it has to do with the new LDAP auth stuff. That's why I left it in the queue and CCed both of them. In the meantime this isn't helping Guillermo get any work done (I figured someone would grab it faster than that). I just reset his password, but the bug still remains that Verbatim and the password reset app are broken with the current password requirements.
Assignee: justdave → server-ops
The new password I just reset him to didn't work. I reset it a second time and that one did. I didn't keep a copy of what it reset it to the first time, but there's definitely something wrong with the paswordreset tool, too...
Assignee: server-ops → oremj
Summary: reset LDAP pasword for : Guillermo Movia → freshly-reset passwords often don't work on the passwordreset page
Just for the records, the first reset (that didn't work) was uu8uTie
Do you still have the email? The generated passwords it does for the resets are always 8 characters, the one you just gave was only 7.
This is the copy/paste of the email: Hi, Your current LDAP password is set to: uu8uTie" Instructions to change your password are at https://ldap.mozilla.org/passwordreset/. Please change it ASAP. This will be your password for all applications that auth off LDAP. Thank you, SysAdmins.
Ah, that quote mark at the end was actually part of the password.
A possible idea for the password reset mail Your current LDAP password is set to --> uu8uTie" <-- Or something like that, to make it more obvious that all of the characters are part of the password.
Added Dave's suggestion.
Status: REOPENED → RESOLVED
Closed: 17 years ago17 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.