Community
Participate
Working Groups
This is a follow-up to bug 322896. This bug is about to address the following situation: "Another scenario where this hurts is when you work with 2 workspaces that share the same secure storage location (the default). After changing a password in one workspace, the other workspace does not see the update. I would expect it to read the current contents of the storage at least when a stored password failed and the user is asked for a new password. Currently, the user has to update a password in all open workbenches, or he has to close all instances of Eclipse except for one, then change the password there, and then restart also that last Eclipse instance before restarting the others." My first thought in bug322896, comment 8 was that one solution could be to listen to changes in a particular CVS node from secure preferences. The question is: is there an Secure Storage API that would allow us to do so? Oleg, any tips?
(In reply to comment #0) > The question is: is there an Secure Storage API that would allow us to do so? No, sorry, that's a known limitation. You'll need several parts that are not there: (1) noticing that external data (password file, keyring, whatever OS uses...) has changed; (2) implementing and notifying listeners; (3) some merge/diff for the data. The (2) is straightforward; the (1) will likley need some effort (different mechanisms from OS's are used); the (3) needs more effort than anybody was willing to spend. If anybody wants to make a patch for the secure storage to implement those pieces, I'll try to do my best to follow up on it.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
