renewal of cert on iButton doesn't work, and no error msg

RESOLVED INCOMPLETE

Status

Core Graveyard
Security: UI
P2
normal
RESOLVED INCOMPLETE
17 years ago
a year ago

People

(Reporter: Christina Fu, Unassigned)

Tracking

({qawanted})

1.0 Branch
x86
Windows 2000
qawanted

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [kerh-coz])

(Reporter)

Description

17 years ago
N6 2001090503, CMS4.2 sp2.
originally have a cert signed by a 3-deep ca, cfu3, on iButton.  Use it to go to
cfu3 (https://cfu:1027) to renew.  The blank page returned, as reported in
http://bugzilla.mozilla.org/show_bug.cgi?id=98203

Look in Manage Certificate on my browser and don't see the cert renewed.
go to the "List Certificates" on cms (https://cfu:1027) and found the new cert
there (renewal was successful, as far as cms is concerned).  Click on "import
cert" and don't see any error/success message.  Look in "Manage Certificate" on
broser again and still don't see the new cert.

Comment 1

17 years ago
qawanted. I'll try to reproduce.
Group: netscapeconfidential?
Keywords: qawanted
Priority: -- → P2
Target Milestone: --- → Future

Comment 2

17 years ago
Marking nEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 3

17 years ago
keyser, are you saying that you have replicated the problem?

Updated

17 years ago
QA Contact: bsharma → junruh

Updated

16 years ago
Blocks: 157818

Updated

16 years ago
Keywords: nsbeta1

Comment 4

15 years ago
adt: nsbeta1-
Keywords: nsbeta1 → nsbeta1-

Comment 5

14 years ago
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 → ---

Updated

13 years ago
Component: Security: UI → Security: UI
Product: PSM → Core

Updated

12 years ago
Whiteboard: [kerh-coz]
QA Contact: junruh → ui

Updated

10 years ago
Version: psm2.0 → 1.0 Branch
Resolving INCOMPLETE for now.  This bug has seen no response in over 6 years.  Please reopen with some current details if this can be reproduced on the latest version of Firefox.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
(Assignee)

Updated

a year ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.