Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
While importing the certificate using the https port and protocol it throws the traceback as Error: Certificate database not initialized.
Version-Release number of selected component (if applicable):
PKI Command-Line Interface 10.4.1-9.el7
How reproducible:
Always
Steps to Reproduce:
## First scenario:
1. pki -d nssdb -c Secret123 -h pki1.example.com -p 20080 client-init
# Initiated the client directory with HTTP port.
2. pki -d nssdb -c Secret123 -h pki1.example.com -p 20080 client-cert-import --ca-server
# Imported the CA Signing cert using HTTP port and imported the admin cert using '--serial 0x6'
# If I try to import another user's certificate with https port and protocol it throws an exception.
3. pki -d nssdb -c Secret123 -h pki1.example.com -p 20443 -P https -n "PKI CA Administrator for Example.Org" client-cert-import --serial 0x54
# see log attachment 1[details]
## Second Scenario:
If I started with the HTTPS client-init.
1. pki -d nssdb -c Secret123 -h pki1.example.com -p 20443 -P https client-init
------------------
Client initialized
------------------
2. pki -d nssdb/ -c Secret123 -h pki1.example.com -p 20080 -P https client-cert-import --ca-server
FATAL: SSL alert sent: RECORD_OVERFLOW
IOException: SocketException cannot write on socket
# see log attachment2[details]
Actual results:
Error: Certificate database not initialized.
Expected results:
It should import the certificate in the client directory.
Additional info:
Hi Asha,
Yes, scenario 2 step #2 is not valid in this bug.
Following is the correct one:
2. [root@pki1 ~]# pki -d nssdb/ -c Secret123 -h pki1.example.com -p 20443 -P https client-cert-import --serial 0x6 "Admin Cert"
Error: Certificate database not initialized.
Sorry for the inconvenience.