pki client-cert-request --extractable command accepts any value.
Steps to Reproduce:
Run pki client-cert-request command pki -d /tmp/nssdbI -c Secret123 -p 20080 client-cert-request "UID=Foo4,E=Foo4@example.com" --extractable 123
Actual results:
[root@pki1 ~]# pki -d /tmp/nssdbI -c Secret123 -p 20080 client-cert-request "UID=Foo4,E=Foo4@example.com" --extractable 123 ----------------------------- Submitted certificate request ----------------------------- Request ID: 44 Type: enrollment Request Status: pending Operation Result: success
Expected results:
It should throw proper error message for boolean value.
Additional info:
[root@pki1 ~]# pki client-cert-request --help usage: client-cert-request [Subject DN] [OPTIONS...] --algorithm <algorithm name> Algorithm (default: rsa) --attribute-encoding Enable Attribute encoding --curve <curve name> ECC key curve name (default: nistp256) --extractable <boolean> Extractable --help Show help options --length <key length> RSA key length (default: 1024) --password Prompt password for request authentication --permanent Permanent --profile <profile> Certificate profile (RSA default: caUserCert, ECC default: caECUserCert) --sensitive <boolean> Sensitive --ssl-ecdh SSL certificate with ECDH ECDSA --transport <path> PEM transport certificate --type <request type> Request type (default: pkcs10) --username <username> Username for request authentication --without-pop Do not include Proof-of-Possession in CRMF request
Per PKI Bug Council of 06/23/2016: 10.3.4
Fixed in master:
Additional change in master:
Metadata Update from @myusuf@redhat.com: - Issue assigned to edewata - Issue set to the milestone: 10.3.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/2503
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.
Login to comment on this ticket.