Howard Chu wrote:
If the actual value doesn't matter, try using a collective attribute
instead.
Thanks, this is exactly what I needed.
I got this working with slapo-collect. I had to hack the schema to
allow the parent object (an organizationalUnit) to have the attributes
that I needed
Hi all -
I've got a familiar story, I'm sure.
I have a campus-wide AD infrastructure that I'd like to leverage.
Unfortunately, my LDAP client (an Isilon NAS) requires some attributes
that AD doesn't populate. e.g., homeDirectory. As it turns out, the
silly thing doesn't even use these
Dan Pritts wrote:
Hi all -
I've got a familiar story, I'm sure.
I have a campus-wide AD infrastructure that I'd like to leverage.
Unfortunately, my LDAP client (an Isilon NAS) requires some attributes that AD
doesn't populate. e.g., homeDirectory. As it turns out, the silly thing
doesn't
