Bug 235880 - [Preferences] Removing a CVS pass from the Password Management page doesn't work
Summary: [Preferences] Removing a CVS pass from the Password Management page doesn't work
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-05 13:14 EDT by Tomasz Zarna CLA
Modified: 2019-09-06 16:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Zarna CLA 2008-06-05 13:14:14 EDT
Build: 3.4 RC3

Bug 222124 introduced Secure Storage as a new way of storing login credentials for CVS connections. At the same time Secure Storage gave us a new place for managing saved passwords[1] which may[2] replace current Password Management pref page[2]. Until then we should make sure that removing a stored password on the Password Management page actually removes it, no matter where it's stored. To achieve that, we will need to update current implementation of the flushCache()[4] method, which calls node.flush(). The new version should call node.clear() which is a proper replacement for Platform.flushAuthorizationInfo[5] used in the past.

[1] General > Security > Secure Storage, Contents tab, CVS tree node
[2] bug 235848
[3] Team > CVS > Password Management
[4] org.eclipse.team.internal.ccvs.core.connection.CVSRepositoryLocation.flushCache()
[5] org.eclipse.core.runtime.Platform.flushAuthorizationInfo(URL, String, String)

Adding Oleg on CC as he's the author the patch from bug 222124.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:12:13 EDT
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.