User Certificate Revocation page should be renamed to Self Certificate Revocation

[pki-bot]

This issue was migrated from Pagure Issue #1525. Originally filed by rpattath (@rpattath) on 2015-07-29 19:02:47:

• Closed at 2018-04-06 14:40:43 as fixed
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1248113

---

EE page: revocation of user certificate does not list all the imported user
certificates

Steps to Reproduce:

goto the ca's eeSSL port and enroll for 2 user certs using the profile
caUserCert

subject name 1 : cn=testuser1,o=example

subject name 2 : cn=testuser2, o=example

goto the ca's agent page and as an agent, approve these certificate requests

goto the ca's eessl port and import these 2 user certificates to the browser.

goto the ca's eessl port and goto the revocation tab

select user certificate.

select a reason to revoke the cert.

click submit.

Actual results:

lists only the cert that was used to login to the EE secure page

Expected results:

Login to the EE ssl page using CA admin cert should list all the imported user
certificates for revocation

[pki-bot]

Comment from edewata (@edewata) at 2015-07-30 01:51:55

The User Certificate Revocation page is actually a self revocation tool because it can only revoke the client certificate that the user used to authenticate to the EE interface. An agent intending to revoke other user's certificate is supposed to use the Revoke Certificates page in the Agent interface instead.

To clarify the distinction, the User Certificate Revocation page probably should be renamed to Self Certificate Revocation.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-08-03 23:55:00

Per CS/DS Meeting of 08/03/2015: 10.3

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-05-06 20:04:05

Per Bug Triage of 05/05/2016: 10.3.2

NOTE: (cfu) I agree with Endi's comment: https://bugzilla.redhat.com/show_bug.cgi?id=1248113#c2
It should just be a simple renaming of the tab

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-06-24 00:14:48

Per PKI Bug Council of 06/23/2016: 10.4

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-12-01 20:54:15

Per Offline Triage of 11/30/2016-12/01/2016: 10.4 - trivial

[pki-bot]

Comment from rpattath (@rpattath) at 2017-02-27 14:04:14

Metadata Update from @rpattath:

• Issue set to the milestone: 10.4

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-09 16:55:20

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-09 16:55:21

Metadata Update from @mharmsen:

• Custom field feature adjusted to None
• Custom field proposedmilestone adjusted to None
• Custom field proposedpriority adjusted to None
• Custom field reviewer adjusted to None
• Custom field version adjusted to None
• Issue close_status updated to: None
• Issue set to the milestone: FUTURE (was: 10.4)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-30 23:25:36

Metadata Update from @mharmsen:

• Issue set to the milestone: 10.5 (was: FUTURE)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-10-25 19:06:45

[20171025] - Offline Triage ==> 10.6

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-10-25 19:06:47

Metadata Update from @mharmsen:

• Issue set to the milestone: 10.6 (was: 10.5)

[pki-bot]

Comment from edewata (@edewata) at 2018-04-06 14:40:46

Fixed in master branch:

• 889e8dd

[pki-bot]

Comment from edewata (@edewata) at 2018-04-06 14:40:47

Metadata Update from @edewata:

• Issue close_status updated to: fixed
• Issue set to the milestone: 10.6.0 (was: 10.6)
• Issue status updated to: Closed (was: Open)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-04-18 19:45:07

Per 10.5.x/10.6 Triage: 10.6.0