#2310 Misleading logs for pkcs12-cert-find and when pkcs12 certificates are improper and used for clone install
Closed: migrated 3 years ago by dmoluguw. Opened 7 years ago by gkapoor.

Below mentioned issues are just to improve logging to debug issues better.

1. Logs are sometimes misleading when we do

pki  pkcs12-cert-find --pkcs12-file
/var/lib/pki/ExternalCA_nss/alias/ca_backup_keys.p12 --pkcs12-password-file
/opt/ExternalCA_nss/ca/pkcs12_password.conf  --debug -v
INFO: Loading PKCS #12 file
NotInitializedException: null

With this input we don't interpret the correct issue.This should be more
meaningful.

2. In case wrong pkcs12 files are used or some import issues we see below
mentioned exception: http://pastebin.test.redhat.com/366482

</pre></p><p><b>root cause</b>
<pre>org.mozilla.jss.crypto.NoSuchItemOnTokenException: Expected user cert but
no matching key?: (-8157) Certificate extension not found.

Steps to Reproduce:

1. Use the cli pki  pkcs12-cert-find --pkcs12-file
/var/lib/pki/ExternalCA_nss/alias/ca_backup_keys.p12 --pkcs12-password-file
/opt/ExternalCA_nss/ca/pkcs12_password.conf
2. Do some import error or use wrong p12 file.

Actual results:

As mentioned above

Expected results:

Logging should be proper so as to ientify issue correctly.

Metadata Update from @gkapoor:
- Issue set to the milestone: UNTRIAGED

7 years ago

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 priority set to: minor (was: major)
- Issue set to the milestone: FUTURE (was: UNTRIAGED)

6 years ago

Metadata Update from @mharmsen:
- Issue assigned to edewata

5 years ago

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=1330449)

5 years ago

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/2430

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

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)

3 years ago

Login to comment on this ticket.

Metadata