While importing the certificate using the https port and protocol it throws the traceback as Error: Certificate database not initialized.
Steps to Reproduce:
## First scenario: 1. pki -d nssdb -c Foobar123 -h pki1.example.com -p 20080 client-init # Initiated the client directory with HTTP port. 2. pki -d nssdb -c Foobar123 -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 Foobar123 -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 Foobar123 -h pki1.example.com -p 20443 -P https client-init ------------------ Client initialized ------------------ 2. pki -d nssdb/ -c Foobar123 -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
Actual results:
Error: Certificate database not initialized.
Expected results:
It should import the certificate in the client directory.
Additional info:
Logs attached in associated bug.
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1462812 - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: minor (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
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/2871
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.