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.
in tools->options-> proxy settings->more user is allowed to set default auth details for security enabled proxy servers if they're in use. Current implementation of AdminAuthenticator does not take this IDE-wide setting into account.
Can you describe how you think the authenticator is supposed to leverage the proxy info? It seems like it would be pretty useless, since the odds that the proxy auth info would apply to some random server (not the proxy) would be pretty low... even in an enterprise setting...
Authenticator knows whether the auth. request is coming from a proxy server or not[1], IDE (or you can perhaps get required info from system properties/JVM directly[2]) knows whether it should use proxy for outgoing connections and if so then whether the proxy server requires authentication. Possible implementation is in o.n.core module[3]. Does this answer your question? [1]: http://java.sun.com/j2se/1.5.0/docs/api/java/net/Authenticator.html#getRequestorType() [2]: see ie. javadoc for o.n.core module [3]: http://hg.netbeans.org/main/file/tip/o.n.core/src/org/netbeans/core/NbAuthenticator.java
answers question: yes... thanks for the additional details...
do you have a set of steps that I can use to reproduce this issue?
do we have any security enabled proxy server I/we could use for testing? basically steps are: -be behind such server -set user credentials in Tools->Options->General->Manual Proxy Settings->Auth... -do some action which will trigger Authenticator.setDefault(AdminAuthenticator) call (start server, deploy or refresh should do that) -create a new javaapp project -create a ws client (or new file->XML->External XMLSchema/WSDL doc) from a resource secured by basic auth and accessible over proxy => one will be asked to provide username/pwd for the proxy as well as most likely for other resources but IDE knows username/pwd for the proxy since it was set in Tools->Options
OK. So you have been able to produce this behavior... how did you do it? You had to be able to set up your environment... So... what authenticating proxy server did you use?
No, I wasn't able to reproduce this, I only checked the code in AdminAuthenticator.java. Steps to reproduce: - setup is described in issue 146720 - very detailed steps for creating secured web service and a client for this service (*) are at http://www.ryandelaplante.com/rdelaplante/entry/ssl_and_http_basic_authentication Other way to reproduce this is to write a unit test similar to one in core module... (*) - see also my comment in desc#6
http://hg.netbeans.org/main/rev/59beabe3ccaa
Integrated into 'main-golden', will be available in build *200809170201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/59beabe3ccaa User: Vince Kraemer <vkraemer@netbeans.org> Log: #138222 : supply proxy auth info when requested from proxy. Also address 138232... don't keep asking for authorization data if the user hits cancel...
Thanks, v.