Certificate import using pki client-cert-import is asking for nss db password when its provided in a file or command line.
Steps to Reproduce:
# pki -d /etc/dirsrv/slapd-CC-NonTMS-LDAP -C /etc/dirsrv/slapd-CC-NonTMS-LDAP/password.txt client-cert-import "CA Certificate" --ca-cert /etc/dirsrv/slapd-CC-NonTMS-LDAP/ca.crt Enter Password or Pin for "NSS FIPS 140-2 Certificate DB": ------------------------------------- Imported certificate "CA Certificate" ------------------------------------- # pki -d /etc/dirsrv/slapd-CC-NonTMS-LDAP -C /etc/dirsrv/slapd-CC-NonTMS-LDAP/password.txt client-cert-import "DS Certificate" --cert /etc/dirsrv/slapd-CC-NonTMS-LDAP/ds.crt Enter Password or Pin for "NSS FIPS 140-2 Certificate DB": ------------------------------------- Imported certificate "DS Certificate" -------------------------------------
Actual results:
Passwords are requested even when its already provided in -c or -C parameter.
Expected results:
Password should be accepted from -c or -C parameter.
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1456597
Fixed in master:
Metadata Update from @edewata: - Issue assigned to edewata
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.7 (was: 10.4) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.7-1.fc27
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/2837
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.