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: Server-Cert created upon using dscreate has Subject:CN =localhost instead of hostname.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux release 8.4 Beta (Ootpa)
389-ds-base-1.4.3.16-3.module+el8.4.0+8869+55706461.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Install 389-ds-instance using dscreate
2. Ensure installation is successful and check the cert created
Actual results:
[root@client slapd-instance4]# certutil -d . -L -n 'Server-Cert'
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
00:b6:ac:b1:48
Signature Algorithm: PKCS #1 SHA-256 With RSA Encryption
Issuer: "CN=ssca.389ds.example.com,O=testing,L=389ds,ST=Queensland,C=
AU"
Validity:
Not Before: Tue Dec 01 11:36:39 2020
Not After : Thu Dec 01 11:36:39 2022
Subject: "CN=localhost,givenName=8e3f42d6-b294-4c21-b62d-482ea6a04a2d
,O=testing,L=389ds,ST=Queensland,C=AU"
Expected results:
CN=localhost should be actually replaced with the actual hostname of the system.
Additional info:
Build Tested: 389-ds-base-1.4.3.16-6.module+el8.4.0+9207+729bbaca.x86_64
[root@ci-vm-XX-XX-XX-XX slapd-TEST]# certutil -d . -L -n 'Server-Cert'
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
00:b6:d7:5b:d2
Signature Algorithm: PKCS #1 SHA-256 With RSA Encryption
Issuer: "CN=ssca.389ds.example.com,O=testing,L=389ds,ST=Queensland,C=
AU"
Validity:
Not Before: Fri Dec 18 10:49:57 2020
Not After : Sun Dec 18 10:49:57 2022
Subject: "CN=<hostname>,givenNam
e=e445d3f3-0593-4607-bcc0-739a4ff41434,O=testing,L=389ds,ST=Queen
sland,C=AU"
Subject Public Key Info:
Public Key Algorithm: PKCS #1 RSA Encryption
RSA Public Key:
Modulus:
'Server-Cert' has Subject: "CN=<hostanme>" where <hostname> is the actual hostname of the system.
-> Marking as verified: tested.
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 (389-ds:1.4 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-2021:1835
Description of problem: Server-Cert created upon using dscreate has Subject:CN =localhost instead of hostname. Version-Release number of selected component (if applicable): Red Hat Enterprise Linux release 8.4 Beta (Ootpa) 389-ds-base-1.4.3.16-3.module+el8.4.0+8869+55706461.x86_64 How reproducible: Always Steps to Reproduce: 1. Install 389-ds-instance using dscreate 2. Ensure installation is successful and check the cert created Actual results: [root@client slapd-instance4]# certutil -d . -L -n 'Server-Cert' Certificate: Data: Version: 3 (0x2) Serial Number: 00:b6:ac:b1:48 Signature Algorithm: PKCS #1 SHA-256 With RSA Encryption Issuer: "CN=ssca.389ds.example.com,O=testing,L=389ds,ST=Queensland,C= AU" Validity: Not Before: Tue Dec 01 11:36:39 2020 Not After : Thu Dec 01 11:36:39 2022 Subject: "CN=localhost,givenName=8e3f42d6-b294-4c21-b62d-482ea6a04a2d ,O=testing,L=389ds,ST=Queensland,C=AU" Expected results: CN=localhost should be actually replaced with the actual hostname of the system. Additional info: