pki-server instance-externalcert-add command prompt for password when invalid token is provided.

[pki-bot]

This issue was migrated from Pagure Issue #2842. Originally filed by mharmsen (@mharmsen) on 2017-10-25 20:18:53:

• Assigned to nobody

---

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.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-10-25 20:20:30

edewata commented:

• negative case

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-10-25 20:20:32

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

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-05-02 19:38:04

Per 10.5.x/10.6 Triage: FUTURE

RHBZ: CLOSED UPSTREAM

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-05-02 19:38:04

Metadata Update from @mharmsen:

• Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1495183)