You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Zoerner (JIRA)" <ji...@apache.org> on 2007/01/13 13:53:28 UTC
[jira] Created: (DIRSERVER-826) User or operational attributes are
missing in search results, if both are requested by a client
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
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
[jira] Reopened: (DIRSERVER-826) User or operational attributes are
missing in search results, if both are requested by a client
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner reopened DIRSERVER-826:
--------------------------------------
I have retetested the issue with a current 1.0.1 build, and in my environment it still persists. I'll attach a test case which demonstrates it.
> 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
> Assigned To: Emmanuel Lecharny
> Attachments: SearchForOperationalAttributesTest.java
>
>
> 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
[jira] Assigned: (DIRSERVER-826) User or operational attributes are
missing in search results, if both are requested by a client
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny reassigned DIRSERVER-826:
-------------------------------------------
Assignee: Emmanuel Lecharny
> 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
> Assigned To: Emmanuel Lecharny
>
> 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
[jira] Updated: (DIRSERVER-826) User or operational attributes are
missing in search results, if both are requested by a client
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner updated DIRSERVER-826:
-------------------------------------
Affects Version/s: 1.5.0
The problem is reproducible in the current trunk version (upcoming 1.5) as well.
> 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
[jira] Closed: (DIRSERVER-826) User or operational attributes are
missing in search results, if both are requested by a client
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner closed DIRSERVER-826.
------------------------------------
I confirm that this one is solved both in 1.0 branch and 1.5.
> 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
> Assigned To: Emmanuel Lecharny
> Attachments: SearchForOperationalAttributesTest.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRSERVER-826) User or operational attributes are
missing in search results, if both are requested by a client
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-826.
-----------------------------------------
Resolution: Fixed
Fixed in 1.0.1 and in 1.5.0
1.0.1 :
http://svn.apache.org/viewvc?view=rev&rev=496351 & http://svn.apache.org/viewvc?view=rev&rev=496372
1.5.0 :
http://svn.apache.org/viewvc?view=rev&rev=496379
> 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
> Assigned To: Emmanuel Lecharny
>
> 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
[jira] Commented: (DIRSERVER-826) User or operational attributes
are missing in search results, if both are requested by a client
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464808 ]
Emmanuel Lecharny commented on DIRSERVER-826:
---------------------------------------------
Ok, I have added another unit test in server-unit, and I confirm there is a pb :
if I request for + and *, I only get user attributes, and no operational attributes.
Other requests are ok.
So it's either in JNDI or in the decoder.
Investigation is going on.
> 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
> Assigned To: Emmanuel Lecharny
>
> 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
[jira] Commented: (DIRSERVER-826) User or operational attributes
are missing in search results, if both are requested by a client
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465305 ]
Emmanuel Lecharny commented on DIRSERVER-826:
---------------------------------------------
ok, I didn't test it, but I have one question :
is the order of + and * relevant?
> 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
> Assigned To: Emmanuel Lecharny
> Attachments: SearchForOperationalAttributesTest.java
>
>
> 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
[jira] Commented: (DIRSERVER-826) User or operational attributes
are missing in search results, if both are requested by a client
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (DIRSERVER-826) User or operational attributes
are missing in search results, if both are requested by a client
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464810 ]
Emmanuel Lecharny commented on DIRSERVER-826:
---------------------------------------------
Only one out of '*' and '+' is added to the attribute list to be returned (the first one, in fact). If we put to real attributes (like 'cn', 'sn'), we get them both, so it' snot a bug in the attribnute's paring. There should be a special case if we have '*' and '+'.
> 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
> Assigned To: Emmanuel Lecharny
>
> 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
[jira] Commented: (DIRSERVER-826) User or operational attributes
are missing in search results, if both are requested by a client
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467378 ]
Emmanuel Lecharny commented on DIRSERVER-826:
---------------------------------------------
I haved included the unit tests in the server (1.0.1 and 1.5.0 versions), and tests are just ok. Is the bug still present ? I guess no.
1.5.0 :
http://svn.apache.org/viewvc?view=rev&rev=499793
http://svn.apache.org/viewvc?view=rev&rev=499794
1.0.1 :
http://svn.apache.org/viewvc?view=rev&rev=499787
> 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
> Assigned To: Emmanuel Lecharny
> Attachments: SearchForOperationalAttributesTest.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-826) User or operational attributes
are missing in search results, if both are requested by a client
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465301 ]
Stefan Zoerner commented on DIRSERVER-826:
------------------------------------------
The attached JUnit test works completely on OpenLDAP 2.3, but the testSearchOperationalAndUserAttributes method (only this) fails with ApacheDS 1.0.1. The behaviour is reproducible with Softerra LDAP Administrator and command line tools (see issue description) as well.
> 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
> Assigned To: Emmanuel Lecharny
> Attachments: SearchForOperationalAttributesTest.java
>
>
> 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
[jira] Updated: (DIRSERVER-826) User or operational attributes are
missing in search results, if both are requested by a client
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner updated DIRSERVER-826:
-------------------------------------
Attachment: SearchForOperationalAttributesTest.java
> 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
> Assigned To: Emmanuel Lecharny
> Attachments: SearchForOperationalAttributesTest.java
>
>
> 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
[jira] Resolved: (DIRSERVER-826) User or operational attributes are
missing in search results, if both are requested by a client
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-826.
-----------------------------------------
Resolution: Fixed
I mark it at resolve as the unit tests does not fail for 1.0.1 nor for 1.5.0.
> 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
> Assigned To: Emmanuel Lecharny
> Attachments: SearchForOperationalAttributesTest.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.