[
https://issues.apache.org/jira/browse/DIRSERVER-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1040:
-----------------------------------------
Here is what we can do, considering the different cases :
1) No attributes are given => it's supposed to behave like if the users has
passed '*'
2) We have only a "1.1" selector => returns nothing (a kind of 'exists' request)
3) We have only a "*" selector => returns all the user attributes
4) We have a list of attributes
4.1) There is no empty attributes, no '*" and no "1.1" => return the requested
attributes
4.2) We have a "*" => returns all the user attributes and the requested
attributes. If they overlap, don't duplicate the attributes (this is usefull to
get operationalAttributes, for instance)
4.3) We have a "1.1" among other attributes=> just ignore "1.1"
4.4) We have an empty attribute => ignore it
I'm positive that all those cases are not handled well either in 1.0.3 or in
1.5.0. I will fix it.
> Unrequested attributes returned on ldap search
> ----------------------------------------------
>
> Key: DIRSERVER-1040
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1040
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0.2
> Environment: ApacheDS 1.0.2
> Java version 1.6.0.02-b06
> Windows XP SP2
> LDAPSEARCH Tools from (both with the same wrong results):
> LDAP SUN SDK4.1 and
> Netscape Directory SDK for java
> Reporter: Ricardo Chicca Junior
>
> Unexpected results for LDAP search operations against ApacheDS server using
> some LDAPSEARH clients. The list of attributes requested is not being
> respected. All attributes are being returned
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
