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:


I am logging this bug because an important customer is having this difference in behavior even if this should not be considered as a bug:


1) copy a custom schema file to /etc/dirsrv/slapd-<server>/schema/

2) schema-reload.pl

3) ldapsearch .... -b "cn=schema" \*  attributetypes objectclasses


in releases till 50 we can see that the clauses MAY and MUST will show the attributetypes with the original case:

 MUST customAttr MAY ( customAttr2 $ customAttr3 $ ...

in releases after 50:

 MUST customattr MAY ( customattr2 $ customattr3 $ ...

A server restart will fix it.

I have detected that the problem comes from this patch:

https://fedorahosted.org/389/ticket/47973

removing it will show the attribute types in the original case.

even if this should not be a bug because the attribute types are case insensitive, as this is provoking issues for the customer, would it be possible to have a correction to show the same behavior ?

Thanks and regards,

German.

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, 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://rhn.redhat.com/errata/RHBA-2017-0667.html