[ 
https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464778
 ] 

Emmanuel Lecharny commented on DIRSERVER-826:
---------------------------------------------

I have added a unit test in 1.0.1, to test this issue. So far, I just added it 
in apacheds-core, so it just checks that the server respond to the request with 
the correct values.

If I request for user attributes ( * ), I just get 'objectClass' and 'ou'
If I request for operational attributes ( + ), I just get 'createTimestamp' and 
'creatorsName'
If I request for both ( * and + ), I get the four attributes

So, from the server side, this is not a bug. Let's now test it on the client 
side : there maybe a problem in the decoder, or in JNDI ...

> User or operational attributes are missing in search results, if both are 
> requested by a client
> -----------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-826
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-826
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0.1, 1.5.0
>            Reporter: Stefan Zoerner
>
> I assume that fixing DIRSERVER-804 had an undesired side effect. Here are two 
> search ops, that work in the current 1.0.1 (default server.xml settings):
> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w ****** -b 
> "ou=system" -s base "(ObjectClass=*)" +
> version: 1
> dn: ou=system
> createTimestamp: 20070113123859Z
> creatorsName: uid=admin,ou=system
> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w ****** -b 
> "ou=system" -s base "(ObjectClass=*)" *
> version: 1
> dn: ou=system
> ou: system
> objectclass: top
> objectclass: organizationalUnit
> objectclass: extensibleObject
> $
> But if someone combines + and * in order to get all the attributes, s/he gets 
> this
> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w ****** -b 
> "ou=system" -s base "(ObjectClass=*)" * +
> version: 1
> dn: ou=system
> createTimestamp: 20070113123859Z
> creatorsName: uid=admin,ou=system
> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w ****** -b 
> "ou=system" -s base "(ObjectClass=*)" + *
> version: 1
> dn: ou=system
> ou: system
> objectclass: top
> objectclass: organizationalUnit
> objectclass: extensibleObject
> Either the operational or the user attributes are missing.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to