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.
Windows 2k version 5.0 running on x86. Netbeans 6 (Build 200711261600) Java 1.6.0_02 Bug Summary: If proxy credentials in Netbeans settings are incorrect, Netbeans will continue to attempt using the (incorrect) settings instead of prompting the user to enter correct details. Expected Result: If credentials are incorrect, Netbeans should prompt for correct credentials. Actual Result: Netbeans repeatedly attempts to connect to proxy server using incorrect credentials. Impact: Say you have the wrong information in your proxy settings and you startup netbeans... (e.g. because your Windows password has expired and you have just changed your password). You start nb. nb attempts to check its website for updates. nb ignores the fact the proxy username/password is wrong and keeps trying. proxy server gets peeved and locks your account. proxy server account is linked to your outlook and windows domain. everything else gets locked out...! And you had no chance to turn the update off or change the settings or anything (because you have to startup nb before you can change the settings). Further Info: I'm not *too sure* if it's repeatedly attempting to connect because I don't have a wireshark session going or anything. I also can't do any testing because it would involve getting my Windows account locked out (at work) and would probably cost several hundreds of dollars in password resets :/
reassign to core for evaluation
reassigning, not sure if this one has been fixed in 6.1 already. OTOH, how do you expect that the IDE will recognize that you have wrong setting not just problem with the connection?
I'll just clarify that I mean the settings have an incorrect username/password, but correct server/ports. i.e. I'd expect some sort of reply from the proxy server to say incorrect username/pass, as opposed to no reply from the server because we're attempting to connect to a bad address.
I dare to say the responsibility for catching and resolving response from server is always on side of caller, e.g. Welcome page. The ProxySelector or java.net.Authenticator just returns proxy/username/password for what are asked for. The caller has to catch response from network and either quit connecting, or invoke the proxy settings customizer. The problem should be address to part of system what repeatedly uses incorrect Proxy settings.
after reading this issue again I thing that it is more enhancement. jgnewell, could you identify when(in what cases) you would expect a response from IDE that user/password is wrong?
Hello, I'd think the possibilities would be as follows: Recognized username + correct password = Good. Unrecognized username + [anything] = Stop and prompt "Incorrect username or password provided". Recognized username + incorrect password = Stop and prompt "Incorrect username or password provided". The bug being that NB doesn't stop and prompt the user for correct details if the credentials are incorrect and repeatedly attempts to use them (leading to an angry Proxy server). Thanks,