The --input parameter for cert-find provides a way to specify the search constraints in an XML file. This parameter doesn't seem to be very userful and there are better alternatives, so it should be removed to avoid confusions.
Consider the following query:
$ pki cert-find --maxSerialNumber 8
The search constraints can be stored in the following XML file:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <CertSearchRequest> <serialNumberRangeInUse>true</serialNumberRangeInUse> <serialTo>8</serialTo> <subjectInUse>false</subjectInUse> <matchExactly>false</matchExactly> <revokedByInUse>false</revokedByInUse> <revokedOnInUse>false</revokedOnInUse> <revocationReasonInUse>false</revocationReasonInUse> <issuedByInUse>false</issuedByInUse> <issuedOnInUse>false</issuedOnInUse> <validNotBeforeInUse>false</validNotBeforeInUse> <validNotAfterInUse>false</validNotAfterInUse> <validityLengthInUse>false</validityLengthInUse> <certTypeInUse>false</certTypeInUse> </CertSearchRequest>
It can be used as follows:
$ pki cert-find --input file.xml
For manual usage or scripting it's better to just use the more user-friendly CLI parameters instead of the XML file. Also there is a Java/Python client library.
Per CS/DS meeting of 04/28/2014 - 10.3.
edewata: 972 is a cleanup issue. ideally it should be 10.2 (and it's easy to fix) but 10.3 is fine too.
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
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/1538
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)