Community
Participate
Working Groups
HEAD, follow-up to bug 286371 > After this [writing password changes to disk immediately] has been fixed, it would be even better if you could reload the > stored passwords whenever a login failed or the user tries to edit a password > (such that changes done in one workspace would immediately be available in > other workspaces running in parallel). To avoid locking accounts due to too many invalid login attempts, the user should be informed that the secure store has been changed on disk. You should only start a second login attempt after the user explicitly agreed to try again with the stored password.
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.
