Monday, April 26, 2021

[389-users] Re: how to configure cn attribute case sensitive

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?

Thank you

Isabella

 

From: Mark Reynolds [mailto:mreynolds@redhat.com]
Sent: Monday, April 26, 2021 4:42 PM
To: Ghiurea, Isabella; General discussion list for the 389 Directory server project.
Subject: Re: [389-users] how to configure cn attribute case sensitive

 

***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:

Hi List,

I need help with the following  ldap   issue , we are running

389-ds-base-1.3.7.5-24.el7_5.x86_64

 

-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...

Regards,

Mark

Thank you

Isabella

 



_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
-- 
 
389 Directory Server Development Team

No comments:

Post a Comment