<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/07/2012 04:51 PM, Snjezana Peco
wrote:<br>
</div>
<blockquote cite="mid:509A8393.1060105@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix"><a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://issues.jboss.org/browse/JBIDE-12368?focusedCommentId=12715308&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12715308">https://issues.jboss.org/browse/JBIDE-12368?focusedCommentId=12715308&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12715308</a>
is also caused by changing the Authenticator.<br>
<br>
</div>
</blockquote>
<br>
oh, so looks like the mess is propagating :( <br>
<br>
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:
<a class="moz-txt-link-freetext" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=196780">https://bugs.eclipse.org/bugs/show_bug.cgi?id=196780</a><br>
The 2 follow-up bugzillas
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=312228">https://bugs.eclipse.org/bugs/show_bug.cgi?id=312228</a>
and
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=299020">https://bugs.eclipse.org/bugs/show_bug.cgi?id=299020</a>
are also not resolved yet, IBM says that they dont have enough
resources.<br>
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. <br>
Not the easiest task at hand, but without that I think we'll keep
having unpredictable results.<br>
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.<br>
<br>
WDYT?<br>
<br>
<blockquote cite="mid:509A8393.1060105@redhat.com" type="cite">
<div class="moz-cite-prefix"> Snjeza<br>
<br>
On 11/7/2012 4:40 PM, André Dietisheim wrote:<br>
</div>
<blockquote cite="mid:509A80DC.6080203@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi Snjezana<br>
<br>
good point! <br>
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.<br>
<br>
Cheers<br>
André<br>
<br>
On 11/07/2012 04:21 PM, Snjezana Peco wrote:<br>
</div>
<blockquote cite="mid:509A7C80.9040800@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">I think you can disable it by
setting your own authenticator.<br>
You can check how ECF sets its authenticator using the
org.eclipse.ecf.provider.filetransfer.retrieve.UrlConnectionRetrieveFileTransfer.UrlConnectionAuthenticator
class and the Authenticator.setDefault method.<br>
<br>
Snjeza<br>
<br>
On 11/6/2012 3:12 PM, André Dietisheim wrote:<br>
</div>
<blockquote cite="mid:50991ADA.2050509@redhat.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hi<br>
<br>
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. <br>
<br>
<a moz-do-not-send="true"
href="https://issues.jboss.org/browse/JBIDE-12999">https://issues.jboss.org/browse/JBIDE-12999</a><br>
<br>
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.<br>
Does anybody know how to disable this in Eclipse? I'm pretty
stuck, I'd appreciate any input.<br>
<br>
Thanks!<br>
André<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>