Bug 30815 - Add Proxy support for any plugin
Summary: Add Proxy support for any plugin
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-03 10:13 EST by Christophe Elek CLA
Modified: 2005-08-04 13:58 EDT (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Elek CLA 2003-02-03 10:13:51 EST
See bug 19258 and bug 22108.
There is a need for an eclipse global set of API and UI to manage proxys and
auto-proxys.
I will cc Core as this team may also need to be involved.
Comment 1 Laurent Fourrier CLA 2003-02-03 15:01:03 EST
For this to be very useful, there is a need to have a password repository. I
don't know if/what eclipse propose now on the subject, but observed usage
patterns of netaccess and common browsers suggest that the user will store once
his password for a proxy/realm/whatever, and forget about it till the next time
he is obliged to change it. So the passwords need to be persisted, and need to
be stored in a secure way. Secure, and reversible, and difficult to decrypt (as
we cannot rely on file system permissions), even with the source code of the
encryption mechanism available to anybody who care to download it. Is there some
mechanism planned to authenticate user at logon in eclipse ?
Comment 2 Christophe Elek CLA 2003-02-04 06:16:54 EST
bug 22108 is supposed to resolve the common authentication.
As of today there are API to access a keystore: 
See org.eclipse.core.internal.runtime.AuthorizationDatabase
Comment 3 Laurent Fourrier CLA 2003-02-04 16:57:31 EST
1) see : http://www.microsoft.com/mind/0599/faq/faq0599.asp for auto proxy
configuration description
2) org.eclipse.core.internal.runtime.AuthorizationDatabase has 2 limitations :
2a) it is internal, and as such, if I remember the doc, subject to change ;)
2b) It expect (by default) to work on urls and realms. Example of real life pac
files suggest that the url is unknown at first, and the proxy is selected by
pattern matching. So, I think there is a need to have some urlAnalyzer,
parametrized from a pac file, which determine the id of the (user,password) pair
to use for a given connection. Once this id is calculated, all the
url/realm/scheme of AuthorizationDatabase can be forgotten.
3) One other problem I see, and it is more a java one : there is presently (as
of JDK 1.4) only one default authenticator for the whole jvm (correct me if I'm
wrong). How are we supposed to manage the case when one eclipse needs to have
two (or more) connections to different servers simultanously, using differents
proxies ?
Comment 4 Laurent Fourrier CLA 2003-02-04 16:59:30 EST
see also : http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html
Comment 5 Tod Creasey CLA 2005-08-04 13:58:23 EDT
I am going to mark this as WONTFIX as this is a stale request