Community
Participate
Working Groups
We need to provide a comman URL authentication Mechanism without the WebDav Support Right now, the first plugin to register a java.net.Authenticator will be called for all plugins. We should provide an Eclipse way to register an Authenticator for a specific site (realm ???) Other plugin should be able to 1) set the Authentiction information using API from Platform 2) request to handle if the wuthentication for their site fails We can also fail over to the next authenticator if a previous one for the same site failed. We should prevent malicious authenticator that send userid and password on the net though ;-)
Having studied a little the question when I first worked on a correction of bug 19258, I think there should be only one authenticator. It can used Delegates, but there should be only one Authenticator, set as default. (And I think that the platform should regularly ensure that the default authenticator is the correct one.) Now, for the Delegates, they should be able to register regexp about the protocol, the hosts, ... and provide information when a match occurs. If several matches occurs, we can try until one pass, or manage priorities, or... If netaccess (or whatever the name of the correction of 19258) is to use the authentication framework, this framework must be available very early in the startup of the platform (as netaccess must be loaded before any plugin depending on the fonctionnality).
Not planning to add this to Eclipse.
Reopening to mark as a duplicate
*** This bug has been marked as a duplicate of 148831 ***
