#2749 Expired certificates are not moving to CRL
Closed: migrated 3 years ago by dmoluguw. Opened 6 years ago by mharmsen.

Expired certificates are not moving to CRL .

Steps to Reproduce:

1. Create a certificate using CaUserCert.Expire the certificate.
2. Now since this certificate is expired it should be visible as "Expired" in CA Agent page.

Issue 1 : Even if we check "show expired certs" for a CRL issuing point from console,Expired certificates are not shown.

Issue 2: If we have two certificates :
0x35 -- Revoked 
0X36 -- Expired

On CA Agent page --> List certificate  
Lowest serial number    0x36    (leave blank for no lower limit)
Highest serial number   0x38    (leave blank for no upper limit)

(check)Do not show certificates that have been revoked
(check)Do not show certificates that have expired or are not yet valid

Output:
Serial number   Status  Subject name
0x34    valid   
UID=revokecert4

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1462308
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue priority set to: critical
- Issue set to the milestone: 10.4

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

6 years ago

During TRIAGE, moved this back to 10.4 for resolution

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.4 (was: 10.5)

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

6 years ago

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

6 years ago

Per 10.5.x/10.6 Triage: 10.6

alee: seems like a trivial usability fix.

Metadata Update from @mharmsen:
- Issue priority set to: minor (was: major)

5 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2869

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata