From: Brent Bice (bbicesgi.com)
Date: Mon Mar 31 2008 - 19:45:02 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    I tried setting an attribute that pointed to an ldap DN and
specified that attribute using "special_result_attribute" in a .cf file
for configuring an ldap-based alias map and that worked dandy.

    But if I have an attribute that contains an LDAP URI that refers to
more than one LDAP record or pointing to another search filter the map
doesn't work. If the attribute contains (for example) something like:
ldap://ldapserver:389/dc=base??sub?(building=10)
the postmap test doesn't fail but even though the above query
(building=10) should yield more than one ldap record the postmap test
only finds the first one.

    Is this by intent? I'm assuming it's just because the code intends
special_result_attribute to return only DNs or URIs that point to a
single LDAP record?

    What I'm looking at doing (maybe) is having an alias like
bldg10mydomain use ldap to find all the people whose ldap records have
an attribute saying they're in building 10. Obviously, I could create a
groupOfUniqueNames object containing a bunch of uniqueMember attributes
pointing to DNs of people in that building. But in the current schema
the building is specified as an attribute of the user, not a group object.

    I was hoping I could just specify another ldap query string in an
attribute and have special_result_attribute pick that up and do another
query. :-)

    Any ideas?

Brent

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]