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/
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:
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,
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.