#3127 Inconsistent error messages for revoked & expired certs
Closed: migrated 3 years ago by dmoluguw. Opened 4 years ago by edewata.

In PKI 10.5 the pki CLI generates CERTIFICATE_EXPIRED and CERTIFICATE_REVOKED messages for expired and revoked certificates, respectively. In PKI 10.6 the error message have changed and become more vague. It should display the same error messages as in PKI 10.5.

Steps to Reproduce:

  1. Go to terminal and fetch certs or profile with Revoked Cert:

[root@pki1 ~]# pki -d /opt/pki/certdb/ -P https -p 20443 -h pki1.example.com -c SECret.123 -n "CA_AdminR" ca-profile-show caUserCert
PKIException: Unauthorized

  1. Go to terminal and fetch certs or profile with Expired Cert:

[root@pki1 ~]# pki -d /opt/pki/certdb/ -P https -p 20443 -h pki1.example.com -c SECret.123 -n "CA_AdminE" ca-profile-show caUserCert
FATAL: SSL alert received: CERTIFICATE_UNKNOWN
IOException: SocketException cannot write on socket

Actual results:

Getting 'CERTIFICATE_UNKNOWN' error for expired certs and 'Unauthorized' error for revoked certs.

Expected results:

It should trigger 'CERTIFICATE_REVOKED' for revoked certs & 'CERTIFICATE_EXPIRED' for expired certs.


Metadata Update from @edewata:
- 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=1656964
- Custom field type adjusted to None
- Custom field version adjusted to None

4 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/3244

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