dogtagpki

#1661 Expired certificates are not moving to specified issuing point
Closed: invalid Opened by gkapoor.

Closed: invalid
Reopen Issue

enable 'include expired certificates' under 'format' in pkiconsole .
In case of invalid certificate it should move to respective issuing point but
it doesn't happen.

Steps to Reproduce:

1. Add few issuing points like mastercrl,mastercrl1,mastercrl2 etc.
2. Under mastercrl2 enable "include expired certificates" and under rest of
issuing point don't enable this setting.
3. now restart pki-ca services.
4. generate a certificate request on CA end entity.
5. Goto CA agent. List certificate.Change the certificate expiry date to 20 sep
2015.
6. Now change the system date to 22 Sep 2015.
7. Restart pki-ca services.
8. After restart ideally the certificate should be in expired state.

Actual results:

We are not able to see this certificate under mastercrl2.

Expected results:

Expired certificate should be shown under mastercrl2.

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1263285 (Red Hat Certificate System)

Per CS/DS meeting of 11/02/2015: 10.4

Moved associated RHCS 9.x Bugzilla to Target Milestone: Future.

Closed as WONT FIX for RHCS 8.x version of product.

Metadata Update from @gkapoor:
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue set to the milestone: 10.4 (was: UNTRIAGED)

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

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

Metadata Update from @mharmsen:
- Issue close_status updated to: invalid
- Issue set to the milestone: 10.5 (was: FUTURE)
- Issue status updated to: Closed (was: Open)

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

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/2220

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
None
None
None
None
Normal
defect
CA
QE
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.