CMCRevoke is exits with displaying no of parameters which are given.
Steps to Reproduce:
1. CMCRevoke -d /etc/dirsrv/slapd-RootCA/ -n "testuser2" -i "CN=CA Signing Certificate,O=Example.Org" -m 6 -p Secret123 -h internal -c "Testing"
Actual results:
Wrong number of parameters:14 Usage: CMCRevoke -d<dir to cert8.db, key3.db> -n<nickname> -i<issuerName> -s<serialName> -m<reason to revoke> -p<password to db> -h<tokenname> -c<comment> 0:-d 1:/etc/dirsrv/slapd-RootCA/ 2:-n 3:testuser2 4:-i 5:CN=CA Signing Certificate,O=example.org 6:-m 7:6 8:-p 9:Secret123 10:-h 11:internal 12:-c 13:Testing
Expected results:
Shows something error message.
The "Wrong number of parameters:14" gives you enough info as an error message.
Looking at the Usage closely, there isn't supposed to be spaces between those - and it's value?
Try: CMCRevoke -d/etc/dirsrv/slapd-RootCA/ -n"testuser2" -i"CN=CA Signing Certificate,O=Example.Org" -m6 -pSecret123 -hinternal -c"Testing"
The Usage provided is clear and correct. Closing as not a bug. If there is still issue, let me know.
Metadata Update from @akahat@redhat.com: - 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: invalid (was: Invalid) - Issue set to the milestone: 10.4.0 (was: 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/2527
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.