Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LDAP-303: odm: missing objectClass inheritance #338

Open
spring-projects-issues opened this issue May 19, 2014 · 1 comment
Open

LDAP-303: odm: missing objectClass inheritance #338

spring-projects-issues opened this issue May 19, 2014 · 1 comment

Comments

@spring-projects-issues
Copy link

Torsten Werner (Migrated from LDAP-303) said:

I have a class with annotation
@entry(objectClasses = {"top"})
but several ldap nodes have only the objectClass=inetOrgPerson which is correct because inetOrgPerson inherits from top. Spring-ldap submits a query
(&(objectClass=top)(uid=...))
to the server and the server responds with all nodes because it knows about the inheritance. For nodes with objectClass=inetOrgPerson only the server sends only this objectClass back to the client without the inherited objectClass top.

But there is a check in org.springframework.ldap.odm.core.impl.DefaultObjectDirectoryMapper#mapFromLdapDataEntry
if(!collectionContainsAll(objectClassesFromJndi, metaData.getObjectClasses()))
that throws away all results that do not have an explicit objectClass=top in the server's response.

IMHO, spring-ldap should trust the ldap server and do not throw away such results. But at least there should be an option for disabling/enabling this extra check.

@christophs78
Copy link

Same issue like #340

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants