pki-server instance-externalcert-add command will prompt for the password when token name is invalid. It should throws the error like no such token.
Steps to Reproduce:
1. pki-server instance-externalcert-add -i topology-02-CA --cert-file /tmp/tempCert.pem --trust-args ',,' --nickname user --token asodjfl 2. It imports the certificate in the CA's alias directory. 3. If certificate is manually deleted (using certutil) and again try to add then it shows following result : pki-server instance-externalcert-add -i topology-02-CA --cert-file /tmp/tempCert.pem --trust-args ',,' --nickname user --token asodjfl ERROR: Certificate already imported for instance topology-02-CA.
Actual results:
Enter password for asodjfl: certutil: could not find the slot asodjfl: SEC_ERROR_NO_TOKEN: The security card or token does not exist, needs to be initialized, or has been removed. ------------------------------------------------- Certificate imported for instance topology-02-CA. -------------------------------------------------
Expected results:
It should throw the error if token is invalid, and not show the certificate imported message.
edewata commented: * negative case
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1495183 - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: FUTURE
Per 10.5.x/10.6 Triage: FUTURE
RHBZ: CLOSED UPSTREAM
Metadata Update from @mharmsen: - Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1495183)
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/2962
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.