eDir to OID via LDAP.

We have extended schema/aux class attributes, as does OID

I believe, because they're aux class attributes, we don't (or can't) put
them into the schema mapping policy?


How to do a matching policy based upon the aux class attribute?

kjhurni's Profile: https://forums.netiq.com/member.php?userid=322
View this thread: https://forums.netiq.com/showthread.php?t=48533