Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2057064

Summary: [RFE] No option to create a private key/CSR with dsconf/Cockpit
Product: Red Hat Directory Server Reporter: mreynolds
Component: cockpit-389-dsAssignee: Jamie Chapman <jachapma>
Status: CLOSED ERRATA QA Contact: LDAP QA Team <idm-ds-qe-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 12.0CC: idm-ds-dev-bugs, pasik, tbordaz, vashirov
Target Milestone: DS12.2Keywords: FutureFeature, Triaged
Target Release: dirsrv-12.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sync-to-jira
Fixed In Version: redhat-ds-12-9020020230314150545.1674d574 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-30 09:40:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mreynolds 2022-02-22 16:44:39 UTC 
Issue Description

There's no way to create a private key and a CSR with dsconf/Cockpit.
However, features for importing a certificate exists, but DS also requires the private key in the NSS database to use the certificate.


Workaround

Users must create the private key and then the CSR with certutil in DS's NSS database (same as in the past).
Then the CSR can be used to request a certificate from the CA and, later, the certificate can be imported with dsconf/Cockpit.
Comment 1 mreynolds 2022-02-22 16:46:13 UTC 
Upstream ticket: 

https://github.com/389ds/389-ds-base/issues/3604
Comment 11 errata-xmlrpc 2023-05-30 09:40:35 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (redhat-ds:12 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:3344