Hi, I can't remember my LDAP password. Please reset my LDAP passwords. Thanks
Assignee: infra → nobody
Severity: blocker → normal
Component: Infrastructure: LDAP → MOC: Service Requests
QA Contact: lypulong
Assignee: nobody → desktop-support
Component: MOC: Service Requests → Servicedesk
QA Contact: lypulong → moconnor
(In reply to Danishka from comment #0) > Hi, > > I can't remember my LDAP password. > Please reset my LDAP passwords. > > Thanks Hello Danishka, I can help you with this. Can you provide your original LDAP request bug for reference? We will need this before proceeding with the LDAP password reset.
Assignee: desktop-support → pdang
Hi Patrick, My LDAP ID is email@example.com.
(In reply to Danishka from comment #2) > Hi Patrick, > > My LDAP ID is firstname.lastname@example.org. Hello Danishka, Please provide us with the original bug # of your original LDAP request. Thanks
I can't remember it as it was created in 2008. This was the recent password reset. https://bugzilla.mozilla.org/show_bug.cgi?id=469996
Danishka: if you look on this page there is a link "my dashboard". Click there and then choose "my bugs" from the dropdown (I think at the bottom). I think you should be able to find your bug that way. Hope this helps
It wont show closed tickets. Btw, why I should provide very first ticket? Whats the purpose of having it if I gave my LDAP ID? If you are not sure about my access, please check with Axel who was with Mozilla when I request my access in 2007/2008.
I guess that would be bug 440745 (CVS account in bug 407648). Having said, the need for the initial bug seems quite counterintuitive.
The need for the initial bug is a requirement from our security team. Thanks for providing the bug #. Your password has been reset. Please confirm if you've received it.
Thanks all! I have rest my password. Thanks again! Closing the bug.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
(In reply to Danishka from comment #9) > Thanks all! > I have rest my password. > > Thanks again! > Closing the bug. You're welcome!
You need to log in before you can comment on or make changes to this bug.