Community
Participate
Working Groups
I added bugzilla.mozilla.org to the list of repositories and restarted Eclipse without checking save password. After a few failed background synchronizations my account was locked due to excessive login failures. This is the email I got: Your Bugzilla account was locked, as the maximum number (5) of failed logins was exceeded. To unlock your account, visit the following link: https://bugzilla.mozilla.org/token.cgi?t=...&a=unlock_account The login attempts occurred from these IP addresses: xxx.xxx.xxx.xxx at 2009-09-10 21:30:22 xxx.xxx.xxx.xxx at 2009-09-10 21:30:22
Wow. I've never seen that happen before. Guess I'll need to implement bug#208839 sooner then later.
In Bugzilla 3.6 the following feature was added: * Users are now locked out of their accounts for 30 minutes after trying five bad passwords in a row during login. If your password is missing or mangled when you start eclipse then you can easily hit this limit, by opening a few tasks. If your BugMail is turned off (BugMail is somewhat redundant when you use Mylyn) then you will not receive any email and there is no way to unlock your account, aside from waiting. In 3.6 I'm not sure if the email would allow you to unlock your account or just makes you wait for 30 minutes. Bug #208839 seems more important given these recent changes to Bugzilla, IMO.
Rob, can you please consider prioritizing this bug accordingly? This may require some support in the framework to track failed attempts accross operations.
I just experienced the same problem with bugs.eclipse.org. We need to do something about this. The connector should at least stop authenticating when the login fails to avoid locking the account. Frank, it'd be great if you could look into this for 3.6 if you have some time.
(In reply to comment #4) > I just experienced the same problem with bugs.eclipse.org. > > We need to do something about this. The connector should at least stop > authenticating when the login fails to avoid locking the account. Frank, it'd be > great if you could look into this for 3.6 if you have some time. OK I try to find the source of this problem
Created attachment 196297 [details] patch V1 Steffen, is it OK that I define ERROR_EMPTY_PASSWORD in mylyn/tasks/core/RepositoryStatus for fix this issue?
Created attachment 196298 [details] mylyn/context/zip
Created attachment 196299 [details] patch V2 Sorry patch V1 introduce some errors in the junit tests
Created attachment 196300 [details] mylyn/context/zip
Thanks! Can you add a test case? Otherwise, please feel free to go ahead an commit this patch.
Created attachment 196835 [details] patch V3 committed patch
Created attachment 196836 [details] mylyn/context/zip
test case is now in HEAD! So we can close this bug.
