Summary: | Persist authenticated passwords in secure storage | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | John Arthorne <john.arthorne> |
Component: | Team | Assignee: | Platform Team Inbox <platform-team-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | bvitale3002, dak2009, Geert.Poels, henrich.kraemer, jluo, Michael.Valenta, nobs, pascal, Szymon.Brandys |
Version: | 3.4 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
John Arthorne
2008-04-29 11:57:52 EDT
This is actually the authentication dialog from org.eclipse.ui.net that is coming up. I'm going to move this to Net team as an enhancement to persist authenticated passwords across sessions in the equinox secure store The issue with this is that the java.net authenticator is not given much context so it doesn't know if it is being asked for a password because of an authentication failure or not. If we use the secure storage, we would need to come up with a strategy for determining whether to provide the password that is stored or not. A simple strategy that may work is this: - If the authenticator is called and there is no password stored, prompt and record that a password was provided - If the authenticator is called and there is a password - if the password was not previously provided, provide it and record that it was provided - if the password was previously provided, assume that authentication failed, discard the password and prompt for a new one *** Bug 115371 has been marked as a duplicate of this bug. *** *** Bug 247279 has been marked as a duplicate of this bug. *** It might be too late for 3.5, but this would be really nice to have. For those who need a workaround, it appears that if you just cancel the first dialog, the second one that surfaces has the appropriate check box, and does persist the password. I guess that's what I'll have to tell our users :) (In reply to comment #5) > For those who need a workaround.... The work around does not work if the Eclipse IDE has been installed as a "shared install" (described in "Eclipse multi-user installs" help page). In a "shared install" environment the IDE does not save the password. I am no longer involved in Platform Team/Compare development. |