(mail=) has no value - I think this should be an error somehow - need to check the ldapv3 specs
Does the following filter conform ldap RFC "(mail=)"
String representation of search filter (http://tools.ietf.org/html/rfc4515#section-3): The filter "mail=" is a 'simple item' with 'filtertype' being 'equal': simple = attr filtertype assertionvalue equal = EQUALS The assertionvalue is compose of N elements (normal or espaced), where N is at 0. assertionvalue = valueencoding valueencoding = 0*(normal / escaped) normal = UTF1SUBSET / UTFMB escaped = ESC HEX HEX
Following that RFC, the string representation "(mail=)" is valid in the ldapsearch command
Filter definition in LDAP protocol (http://tools.ietf.org/html/rfc4511#section-4.5.1) The filter "mail=" is 'equalityMatch' of an AttributeValueAssertion (http://tools.ietf.org/html/rfc4511#section-4.1.6) The 'assertionValue' is a an OCTET STRING that can be 0 length
Following that RFC, this filter is also valid.
'mail' is IA5 String that is a string of zero,one or more char. If I update an entry with an empty 'mail' value ^dn: uid=x4,dc=com$ ^changetype: modify$ ^add: mail$ ^mail:$
This filter is supperted by RHDS, ODSEE. Will check OpenLDAP DS
It seems this ticket can be closed as NOTABUG?
Replying to [comment:9 nhosoi]:
As mentioned in https://fedorahosted.org/389/ticket/47524?replyto=9#comment:3, the filter '(mail=)' is a valid filter. Closing that ticket as not a bug
Metadata Update from @tbordaz: - Issue assigned to tbordaz - Issue set to the milestone: 1.3.3 backlog
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/861
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.