Closed
Bug 98972
Opened 23 years ago
Closed 16 years ago
auto-cert-select needs memory
Categories
(Core Graveyard :: Security: UI, enhancement, P2)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 395399
People
(Reporter: lord, Unassigned)
References
Details
(Whiteboard: [kerh-ehz])
Attachments
(1 file)
15.58 KB,
image/gif
|
Details |
Advanced users like to set their prefs to use manual certificate selection so
the client asks which cert to use each time the server requests one.
One problem with manual-cert-select is that the order of the popup selections
does not vary from session to session. That's fine if the cert that the user
always uses for that site is at the top of the list. But often the cert the
user wants to use will appear below the top line.
The client should have some way of remembering past decisions to reduce the
number of clicks the user has to make to login to a web site.
Options include:
(1) Sort the list alphabetically, but set the default to be the cert the user
used last time this dialog was used. That may mean that the default is set to a
line in the middle of the list.
(2) Sort the list alphabetically, but add a "Remember this decision" checkbox.
Updated•23 years ago
|
Priority: -- → P2
Target Milestone: --- → Future
Updated•23 years ago
|
QA Contact: bsharma → junruh
Comment 3•21 years ago
|
||
Mass change "Future" target milestone to "--" on bugs that now are assigned to
nobody. Those targets reflected the prioritization of past PSM management.
Many of these should be marked invalid or wontfix, I think.
Target Milestone: Future → ---
Updated•19 years ago
|
Severity: normal → enhancement
Whiteboard: [kerh-ehz]
Updated•18 years ago
|
QA Contact: junruh → ui
Updated•17 years ago
|
Blocks: clientauth
Comment 4•16 years ago
|
||
I believe this idea is more actively covered by bug 395399. If this is not the same issue please reopen and clarify.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•