Thank you Mark, William for reply , how about this user attribute : “DistinguishedName” in our DS this is matching the cn attributes for string values .
Should we consider to enable “Case Exact Match “ for this last attribute and rebuild the index?
***ATTENTION*** This email originated from outside of the NRC. ***ATTENTION*** Ce courriel provient de l'extérieur du CNRC
On 4/26/21 3:34 PM, Ghiurea, Isabella wrote:
I need help with the following ldap issue , we are running
-how to check if 389-DS is cfg to be case sensitive?
- how to cfg the cn attribute which is indexed in my DS to be case sensitive ?
Sorry, you can't (shouldn't). "cn" is a standard attribute with a predefined syntax. "cn" is used internally by the server for many things, and it is expected to be case insensitive. Making it case-sensitive could break things in ways that would be very difficult to troubleshoot. You should never attempt to modify the server's core schema. Especially "cn" - just look at all the entries under cn=config...
_______________________________________________389-users mailing list -- email@example.comTo unsubscribe send an email to firstname.lastname@example.orgFedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelinesDo not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
389 Directory Server Development Team