This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ BUILD # : 200904150201 ] [ JDK VERSION : 1.6.* ] NOTE: This is evident for accounts that lock after 3 bad authentication attempts. 1. Check out a project in NetBeans IDE from CVS, using :ext: SSH method and tick the save password option. 2. Perform CVS tasks to ensure password has persisted. 3. Close the IDE 4. Delete ~/.netbeans/dev 5. Start IDE and open the checked out project 6. Try performing CVS update 7. Account will become locked. * I have now discovered a workaround. between points 4 and 5 do the following: 1. Go to Team > CVS > Checkout... 2. Enter the CVS address and tick Remember Password 3. Click "Next >" 4. Resume point 6, account will not become locked.
I tried this myself and I faced no locked account. By the way, what does it mean Brett? When I checked "Remember Password" option it didn't require the password on the next sessions. If I deleted my userdir, authentication failed and I was prompted for the password again. This is with #200904210201.
If I type my password incorrectly 3 times in a row the account becomes locked. It seems that each time I reinstall netbeans my account becomes locked only after one password attempt. This isn't a huge problem for me as I'm only getting this because I'm updating to newest dev builds each day.
I have the same issue, it happens when I change my password on the CVS server, NETBEANS tries more than 35 times to connect to that server, via SSH and the password cached in NETBEANS is the old incorrect password. The CVS server puts a lock on my account because of excessive logon failed attempts and I have to contact the server admin to unlock the account Could I set the number of retry attempts somehow? or just have it prompt my for a password after 1 failed attempt? I'm thinking a work around could be to delete the password from NETBEANS prior to the server password change, but I always seem to forget to do that, would be better if I could lower the ammount of retry attempts for NETBEANS