When invalid date is passed to --revokedOnTo and --revokedOnFrom, i still see results getting returned
[root@dhcp207-176 dogtag]# pki cert-find --revokedOnTo 2044-33-33 --size 1000 --------------- 2 entries found --------------- Serial Number: 0xe Subject DN: UID=CA_adminR,E=CA_adminR@example.com,CN=CA_Admin_RevokedCert,OU=Engineering,O=Example,C=US Status: REVOKED Type: X.509 version 3 Key Algorithm: PKCS #1 RSA with 2048-bit key Not Valid Before: Tue Jul 15 10:56:38 EDT 2014 Not Valid After: Sun Jan 11 09:56:38 EST 2015 Issued On: Tue Jul 15 10:56:42 EDT 2014 Issued By: caadmin Serial Number: 0x11 Subject DN: UID=CA_agentR,E=CA_agentR@example.com,CN=CA_Agent_RevokedCert,OU=Engineering,O=Example,C=US Status: REVOKED Type: X.509 version 3 Key Algorithm: PKCS #1 RSA with 2048-bit key Not Valid Before: Tue Jul 15 10:58:29 EDT 2014 Not Valid After: Sun Jan 11 09:58:29 EST 2015 Issued On: Tue Jul 15 10:58:31 EDT 2014 Issued By: caadmin ---------------------------- Number of entries returned 2 ----------------------------
[root@dhcp207-176 dogtag]# pki cert-find --revokedOnFrom 02-2014-07 --size 1000 --------------- 2 entries found --------------- Serial Number: 0xe Subject DN: UID=CA_adminR,E=CA_adminR@example.com,CN=CA_Admin_RevokedCert,OU=Engineering,O=Example,C=US Status: REVOKED Type: X.509 version 3 Key Algorithm: PKCS #1 RSA with 2048-bit key Not Valid Before: Tue Jul 15 10:56:38 EDT 2014 Not Valid After: Sun Jan 11 09:56:38 EST 2015 Issued On: Tue Jul 15 10:56:42 EDT 2014 Issued By: caadmin Serial Number: 0x11 Subject DN: UID=CA_agentR,E=CA_agentR@example.com,CN=CA_Agent_RevokedCert,OU=Engineering,O=Example,C=US Status: REVOKED Type: X.509 version 3 Key Algorithm: PKCS #1 RSA with 2048-bit key Not Valid Before: Tue Jul 15 10:58:29 EDT 2014 Not Valid After: Sun Jan 11 09:58:29 EST 2015 Issued On: Tue Jul 15 10:58:31 EDT 2014 Issued By: caadmin ---------------------------- Number of entries returned 2 ----------------------------
proposing Milestone 10.2.2
Proposed Milestone: 10.2.3 (per CS Meeting of 09/17/2014)
remains low priority
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog
Per 10.2.3 TRIAGE meeting of 02/26/2015: 10.3
NOTE: Moved from 10.2 Backlog since it was not a documentation/man page issue.
Per Bug Triage of 05/03/2016: 10.4
Metadata Update from @mrniranjan: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field lowhangingfruit adjusted to vakwetu: X - 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: UNTRIAGED)
Per 10.5.x/10.6 Triage: FUTURE
RHBZ: CLOSED UPSTREAM
Metadata Update from @mharmsen: - Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1224635)
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/3335
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
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)
Login to comment on this ticket.