------=_Part_27665_28430263.1199452056921 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

Yes, you are completely right. The only reason I can think of using the DN version is because you are forced by your schema (attribute types for the expansion source attribute differ). I emphasize that the implementation of both is quite different. The DN version uses recursivity while the URL version relies in slapd's search-reply mechanism. I just added the first one as an example.

URL version is much more powerful and more elegant. You suggested subGroupURL: ldap:///<dn>??base, but even subGroupURL: ldap:///<dn> works ok (if I remember right).

------=_Part_27665_28430263.1199452056921 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

<br>&nbsp; Yes, you are completely right.&nbsp; The only reason I can think of using the DN version is because you are forced by your schema (attribute types for the expansion source attribute differ). I emphasize that the implementation of both is quite different. The DN version uses recursivity while the URL version relies in slapd&#39;s search-reply mechanism. I just added the first one as an example. <br><br>&nbsp; URL version is much more powerful and more elegant. You suggested subGroupURL: ldap:///&lt;dn&gt;??base, but even subGroupURL: ldap:///&lt;dn&gt; works ok (if I remember right).<br><br>

------=_Part_27665_28430263.1199452056921--