Bug 235848 - [Preferences] Password Management page seems to be obsolete
Summary: [Preferences] Password Management page seems to be obsolete
Status: RESOLVED FIXED
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: 3.5 M6   Edit
Assignee: Tomasz Zarna CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-05 11:17 EDT by Tomasz Zarna CLA
Modified: 2009-02-10 05:20 EST (History)
4 users (show)

See Also:


Attachments
Patch v01 (1.78 KB, patch)
2008-09-16 10:31 EDT, Tomasz Zarna CLA
no flags Details | Diff
mylyn/context/zip (3.50 KB, application/octet-stream)
2008-09-16 10:31 EDT, Tomasz Zarna CLA
no flags Details
Patch v02 (24.68 KB, patch)
2008-09-22 09:46 EDT, Tomasz Zarna CLA
no flags Details | Diff
Patch v03 (24.96 KB, patch)
2009-02-10 04:44 EST, Tomasz Zarna CLA
no flags Details | Diff
Patch v04 (28.60 KB, patch)
2009-02-10 05:16 EST, Tomasz Zarna CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Zarna CLA 2008-06-05 11:17:01 EDT
Since we started to use Secure Storage for managing CVS passwords[1] it seems reasonable to replace "Password Management" preference page[2] with the one introduced by Secure Storage[3].


[1] bug 222124
[2] Team > CVS > Password Management
[3] General > Security > Secure Storage, Contents tab, CVS node
Comment 1 Kevin McGuire CLA 2008-06-05 13:31:30 EDT
You're right, this page doesn't seem to serve any purpose anymore.  

Its probably good to teach people to go to the general Security page to do password management.  The risk of keeping the CVS page is that it may obscure the storage model (ie. who stores them and how).  Also since the CVS passwords are now more strongly stored, its less likely they'll want to delete them.
Comment 2 Oleg Besedin CLA 2008-06-05 14:14:19 EDT
All true except that ability to "manage" individual entries in the secure storage was removed for 3.4 due to reactions like "I do not understand what it is for, delete it".
Comment 3 Oleg Besedin CLA 2008-06-05 14:15:44 EDT
(In reply to comment #2)
> All true except that ability to "manage" individual entries in the secure
> storage was removed for 3.4 due to reactions like "I do not understand what it
> is for, delete it".

I refer here to the secure storage view and context menus on it to add/remove nodes and values.
Comment 4 Tomasz Zarna CLA 2008-06-06 10:56:28 EDT
(In reply to comment #1)
> You're right, this page doesn't seem to serve any purpose anymore.
> 
> Its probably good to teach people to go to the general Security page to do
> password management.  The risk of keeping the CVS page is that it may obscure
> the storage model (ie. who stores them and how).  Also since the CVS passwords
> are now more strongly stored, its less likely they'll want to delete them.

Kevin, you're UI/Usability guru, should I simple remove the page or make it blank with only a link to Secure Storage remaining (+ some comment)?
Comment 5 Kevin McGuire CLA 2008-06-06 14:31:11 EDT
(In reply to comment #4)
> (In reply to comment #1)
> > You're right, this page doesn't seem to serve any purpose anymore.
> > 
> > Its probably good to teach people to go to the general Security page to do
> > password management.  The risk of keeping the CVS page is that it may obscure
> > the storage model (ie. who stores them and how).  Also since the CVS passwords
> > are now more strongly stored, its less likely they'll want to delete them.
> 
> Kevin, you're UI/Usability guru, should I simple remove the page or make it
> blank with only a link to Secure Storage remaining (+ some comment)?

I'd suggest remove the page.

Question though: what happens if someone tries to keep their 3.3 workspace and opens it in 3.4?  Do we move their CVS pass to secure store, or continue to retrieve it from the 3.3 store?

Either way, in the New CVS Repo wizard (and the stand alone password prompt), suggest we have a link pointing to the pref page with some text like "If you later want to manage your password, please see the Secure Storage preference page".  This would work well with the fact that you already say that password entry will trigger secure storage.  That way you train them the right new place to go so don't so much need old page with link to new place.

Comment 6 Tomasz Zarna CLA 2008-06-17 09:41:50 EDT
(In reply to comment #5)
> Question though: what happens if someone tries to keep their 3.3 workspace and
> opens it in 3.4?  Do we move their CVS pass to secure store, or continue to
> retrieve it from the 3.3 store?

Haven't done it, but I'm pretty sure that the user will be asked to reenter all his/her passwords.
Currently, CVS passwords are not migrated to secure storage. See bug 227517.

> Either way, in the New CVS Repo wizard (and the stand alone password prompt),
> suggest we have a link pointing to the pref page with some text like "If you
> later want to manage your password, please see the Secure Storage preference
> page".  This would work well with the fact that you already say that password
> entry will trigger secure storage.  That way you train them the right new place
> to go so don't so much need old page with link to new place.

Sounds good.
Comment 7 Tomasz Zarna CLA 2008-09-16 10:31:32 EDT
Created attachment 112676 [details]
Patch v01

Patch that comments out the old "Password managment" page and removes a reference to this page in User Documentation.
Things to consider: 
* deleting PasswordManagmentPreferencePage 
* deleting ref-19cvs-password.htm help page
* removing (instead of commenting out) extension for the pref page
Comment 8 Tomasz Zarna CLA 2008-09-16 10:31:34 EDT
Created attachment 112677 [details]
mylyn/context/zip
Comment 9 Tomasz Zarna CLA 2008-09-16 10:34:03 EDT
* a link pointing to the new preference page as suggested by Kevin in comment 5
Comment 10 Tomasz Zarna CLA 2008-09-22 09:46:46 EDT
Created attachment 113113 [details]
Patch v02
Comment 11 Tomasz Zarna CLA 2008-10-31 06:50:00 EDT
Szymon could you check if the fix is ok with you? I wanted to release it asap, but I remember you had some questions about the it...
Comment 12 Tomasz Zarna CLA 2008-11-25 05:10:42 EST
There are still some entries appearing in the to-be-removed Password Management page. I would expect the page to have no entries (except those added before we moved to Secure Storage), but as soon as I create a new Repo Location (with a password) it does appear in both the old pass page and the one in Secure Store section. Before we decide to finally remove the old page we should investigate why these entries still appear on the page.
Comment 13 Tomasz Zarna CLA 2009-01-23 10:11:55 EST
Sorry, I haven't managed to investigate it in 3.5M5, hopefully Pawel will find some time for it during 3.5M6.
Comment 14 Pawel Pogorzelski CLA 2009-01-29 07:37:37 EST
(In reply to comment #12)
> There are still some entries appearing in the to-be-removed Password Management
> page. I would expect the page to have no entries (except those added before we
> moved to Secure Storage), but as soon as I create a new Repo Location (with a
> password) it does appear in both the old pass page and the one in Secure Store
> section. Before we decide to finally remove the old page we should investigate
> why these entries still appear on the page.
> 

This is not a problem since the page to be deleted calls CVSRepositoryLocation.getCVSNode() to populate the UI and this method was changed along with the fix for bug 222124 to get data from Secure Storage.

In other words information from secure storage is duplicated on both preference pages now.
Comment 15 Tomasz Zarna CLA 2009-02-10 04:44:19 EST
Created attachment 125214 [details]
Patch v03

Updated patch.
Comment 16 Tomasz Zarna CLA 2009-02-10 05:16:58 EST
Created attachment 125215 [details]
Patch v04

Updated copyright dates and removed keyword extension for the removed pref page.
Comment 17 Tomasz Zarna CLA 2009-02-10 05:20:25 EST
Fixed in HEAD, but filed bug 264318. Available, or I should rather say not available, starting from build I20090210-0800.