Closed Bug 94425 Opened 23 years ago Closed 8 years ago

Implement an on-request OCSP check for the Cert Manager window

Categories

(Core Graveyard :: Security: UI, enhancement, P2)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ssaux, Unassigned)

Details

(Whiteboard: [kerh-ehz])

When OCSP check is enabled, interacting with the Cert Manager window was very
slow (see bug 87654). The reason is that for each cert, a new ocsp check needs
to happen. In fact if the ocsp responder is down, the cert manager would hang
for a long period. Therefore the fix to bug 87654 removed the OCSP check for the
purpose of (and only in this case) displaying information in the cert manager. 
For the next release the proper way would be to let the use check the OSCP
status of a cert on demand.
One possible implementation would let the user select the cert(s) to check and
clik on a "check OCSP" button to do the check.
Needs some UI mock ups and design.
P2
target->future
Priority: -- → P2
Target Milestone: --- → Future
Note that bug 93703 may make this bug unnecessary.
QA Contact: ckritzer → junruh
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
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 → ---
Product: PSM → Core
Severity: normal → enhancement
Whiteboard: [kerh-ehz]
QA Contact: junruh → ui
Version: psm2.1 → 1.0 Branch
Version: 1.0 Branch → Trunk
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.