[
https://issues.apache.org/jira/browse/DIRSERVER-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640055#comment-17640055
]
Mark Dixon commented on DIRSERVER-2371:
---------------------------------------
{color:#172b4d}I think I'm seeing the same, used to work before but now it
fails on AM26. My query is (&(objectClass=*)(uid=tank)) - if I change it to
{color}{color:#172b4d}(&(objectClass=posixAccount)(uid=\{0})), it does work.
Also if I change the seach base from dc=example,dc=com to
ou=users,dc=example,dc=com it also works.
{color}
{color:#172b4d}Data is:{color}
{code:java}
dn: cn=tank,ou=users,dc=example,dc=com
memberOf: cn=publisher,ou=groups,dc=example,dc=com
cn: tank
gidnumber: 501
homedirectory: /home/users/tank
objectclass: inetOrgPerson
objectclass: posixAccount
objectclass: top
objectclass: simulatedMicrosoftSecurityPrincipal
samAccountName: tank
sn: tank
uid: tank
uidnumber: 1001 {code}
> Inclusion of 'top' objectclass in searches yields no results
> ------------------------------------------------------------
>
> Key: DIRSERVER-2371
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2371
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: search
> Affects Versions: 2.0.0.AM26
> Environment: Windows
> Reporter: Carlo Accorsi
> Priority: Minor
>
> Hi, it's been a while since I've posted here and I hope this note finds you
> all well.
> We stayed on a very old ApacheDS version (M17) for many years and have
> finally moved to AM26.
> Many of our queries for users, groups, etc logically AND objectclasses with
> the search criteria. We do this to limit the types of entries that are
> returned in a particular search. For example to find users with CN's starting
> with 'A' the query would look like this.
> (&
> (objectClass=top)
> (objectClass=person)
> (objectClass=organizationalPerson)
> (objectClass=inetOrgPerson)
> (cn=A*)
> )
> This query works in M17, but not AM26.
> If I remove the 'top' value from the query as shown below, it works. I'm
> assuming because it's abstract.
> (&
> (objectClass=person)
> (objectClass=organizationalPerson)
> (objectClass=inetOrgPerson)
> (cn=A*)
> )
> We define objectclasses of entry types in a configuration file. So we easily
> fixed our queries by removing 'top' from the config file. However we have
> functions like isUser, isGroup, isEquipment , etc that take an Entry and
> compare the equality of its objectclass array with values defined in the
> configuration file. This introduced a breaking change for us - which isn't
> horrible and we can fix. However, I'm just wondering if it was intentional to
> return no results when the top objectclass is present in the query?
> Thanks!
> Carlo
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
