On 11/7/2012 5:01 PM, André Dietisheim wrote:
On 11/07/2012 04:51 PM, Snjezana Peco wrote:

oh, so looks like the mess is propagating :(

As I see it the default implementation in org.eclipse.ui should get raised to a level where different plugins can contribute solutions to their needs. The shortcomings of the NetAuthenticator in org.eclipse.ui was filed in 2007 and is still not resolved: https://bugs.eclipse.org/bugs/show_bug.cgi?id=196780
The 2 follow-up bugzillas https://bugs.eclipse.org/bugs/show_bug.cgi?id=312228 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=299020 are also not resolved yet, IBM says that they dont have enough resources.
On top of this one should then convince the different plugins that currently override the NetAuthenticator to drop their Override and use the enhanced mechanism.
Not the easiest task at hand, but without that I think we'll keep having unpredictable results.
Alternatively we could of course also stop using UrlConnection and switch to Apache HttpClient. We would then of course have to watch and read the Eclipse proxy preferences.

WDYT?


The Apache HttpClient doesn't support NTLMv2 authentication.

Snjeza

Snjeza

On 11/7/2012 4:40 PM, André Dietisheim wrote:
Hi Snjezana

good point!
I already found out about this when looking at different Eclipse plugins. EGit does it, Scout and apparently ECF, too. Quite a mess to be honest: A bad API in the jdk UrlConnection, a poor implementation in org.eclipse.ui and here we are: plenty of plugins overriding the Authenticator with unpredictable results.

Cheers
André

On 11/07/2012 04:21 PM, Snjezana Peco wrote:
I think you can disable it by setting your own authenticator.
You can check how ECF sets its authenticator using the org.eclipse.ecf.provider.filetransfer.retrieve.UrlConnectionRetrieveFileTransfer.UrlConnectionAuthenticator class and the Authenticator.setDefault method.

Snjeza

On 11/6/2012 3:12 PM, André Dietisheim wrote:
Hi

In OpenShift tooling I have a dialog that allows you to create/edit connections to OpenShift. Behind the scenes I'm using HttpUrlConnection to talk to the OpenShift REST service. If I provide invalid user-credentials Eclipse pops up a dialog for the user to provide username and password on top of my dialog.

https://issues.jboss.org/browse/JBIDE-12999

It turns out that Eclipse is registering it's very own Authenticator in HttpUrlConnection which is invoking the Eclipse credentials dialog if the Http response is 401.
Does anybody know how to disable this in Eclipse? I'm pretty stuck, I'd appreciate any input.

Thanks!
André





_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev




_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev




_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev