Last Comment Bug 540065 - Unable to delete a Certificate Name folder from Authorities tab
: Unable to delete a Certificate Name folder from Authorities tab
Status: RESOLVED DUPLICATE of bug 78808
Product: Core Graveyard
Classification: Graveyard
Component: Security: UI (show other bugs)
: 1.9.1 Branch
: All All
-- minor (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
Depends on:
  Show dependency treegraph
Reported: 2010-01-15 14:23 PST by Tony Chung [:tchung]
Modified: 2016-09-27 13:03 PDT (History)
3 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Tony Chung [:tchung] 2010-01-15 14:23:44 PST
using Fx3.5.5 and Fx 3.6 rc, i am unable to delete a certificates folder from the Authorities tab.   Deleting individual certs does work, but not the entire folder at once,.   If that's by design, we should disable the "Delete" button in the UI.

1) open prefs > Advanced > Encryption > "View Certificates" button
2) Click Authorities tab
3) Select a folder that has more than one certificate in it.  If nothing, then add one from
4) hightlight the Cert name folder (eg. Verisign, inc), and press "Delete"
5) Verify you cannot delete the folder.   You can delete individual certs in the folder though.

- Either disable the "Delete" button when highlighting a folder, or allow folder deletion support

- unable to delete a certificate folder.
Comment 1 User image Ludovic Hirlimann [:Usul] 2010-01-18 02:00:29 PST
Shouldn't this be in PSM ?
Comment 2 User image Paul O'Shannessy [:zpao] (not reading much bugmail, email directly) 2010-01-18 22:17:48 PST
I hit this too while running the FFTs. I think bug 78808 covers at least your first expected result.
Comment 3 User image :Cykesiopka 2015-03-20 23:38:12 PDT
Bug 78808 changed the UI so that the buttons are disabled if any "folders"/containers are selected, so this is a duplicate in that sense.

Bug 1136338 is about making this process less tedious, e.g. by implementing a way to delete all certs under a container that actually works.

*** This bug has been marked as a duplicate of bug 78808 ***

Note You need to log in before you can comment on or make changes to this bug.