Hello

Seems that the attribute dn/distinguishedname never gets imported/read corretly when using in in Feeds with LDAP Query Fetcher + LDAP Entry Parser for Feeds.

The attribute retrieves no information at all, for example, in the case of LDAP groups.
This would be important to make a match with the memberof attribute in users.

Any ways on how to circumvent this issue? Is it a bug?

Cheers

Comments

lpalgarvio created an issue. See original summary.

lpalgarvio’s picture

lpalgarvio commented

I found the source of the problem.

In LDAP queries:

Attributes to return.
Enter as comma separated list. DN is automatically returned. Leave empty to return all attributes. e.g. objectclass,name,cn,samaccountname

This is an incorrect statement.

When creating a LDAP query, if you input custom attributes to retrieve, but don't include DN/distinguishedName, and then test it, while the query does show these custom attributes and adds the DN automatically as stated (NOTE: but not distinguishedName), when it's consumed by Feeds, the DN (and so is distinguishedName) field that is supposed to be present is entirely ignored.

May i propose some solutions?

  1. Fix the Feeds counterpart to always append the DN field to the list of retrieved fields, even if not included, just as stated in the LDAP query UI
  2. State in this form that distinguishedName is not automatically added, or add it as well to both and state it also in the form
grahl’s picture

grahl
he/him
Location Zürich
commented

Would you consider providing a patch for your preferred variant?

  • grahl committed 51ea7e8 on 7.x-2.x 
    Issue #2692201 by lpalgarvio: LDAP Feeds: dn/distinguished name not...
grahl’s picture

grahl
he/him
Location Zürich
commented
Status: Active » Fixed

To not prolong this issue I've added a sentence asking users to explicitly declare dn.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.