pki pkcs12-import command throws Unrecognized option error when ran with --no-trust-flags option.
Steps to Reproduce:
pki -d /tmp/nssdbI -c Secret123 pkcs12-import --pkcs12-file /tmp/ca_admin_cert.p12 --pkcs12-password Secret123 --no-trust-flags
Actual results:
[root@pki1 ~]# pki -d /tmp/nssdbI -c Secret123 pkcs12-import --pkcs12-file /tmp/ca_admin_cert.p12 --pkcs12-password Secret123 --no-trust-flags Error: Unrecognized option: --no-trust-flags
Expected results:
It should import the cert with proper success message.
Additional info:
[root@pki1 ~]# pki pkcs12-import --help Usage: pki pkcs12-import [OPTIONS] --pkcs12-file <path> PKCS #12 file containing certificates and keys. --pkcs12-password <password> Password for the PKCS #12 file. --pkcs12-password-file <path> containing the PKCS #12 password. --no-trust-flags Do not include trust flags --no-user-certs Do not import user certificates --no-ca-certs Do not import CA certificates -v, --verbose Run in verbose mode. --debug Run in debug mode. --help Show help message.
Per PKI Bug Council of 06/30/2016: 10.4
Metadata Update from @myusuf@redhat.com: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - 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: 10.5 (was: UNTRIAGED)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Per 10.5.x/10.6 Triage: 10.6
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/2516
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.