You can even write an interceptor which will remove the DN from the returned attributes, and add it when the search is successfull (you will have to add a Filter)
I think it can be done in half an hour. Otherwise, I would rather implement RFC 5020, transform the DN to entryDN in an interceptor, and back. That would be way better, but a bit longer :) On Mon, Feb 23, 2009 at 12:21 PM, Yiannis Mavroukakis <[email protected]> wrote: > I've looked around the config for Jabber XCP and it doesn't seem to be a > configurable attribute. Is it possible to use > an interceptor, implement search( NextInterceptor next > ,SearchOperationContext opContext ), and rewrite the attribute to be 1.1 > instead of dn ? > > Thanks, > > Yiannis > > Emmanuel Lecharny wrote: >> >> More specifically, if you just want to get the DN of each entry >> without any other attribute, just specify "1.1 " as requested >> attributes. >> >> On Mon, Feb 23, 2009 at 11:16 AM, Emmanuel Lecharny >> <[email protected]> wrote: >> >>> >>> Hi, >>> >>> DN is not an attribute. You should not send a search request with it >>> as a requested attribute. That's why you get this warning. >>> >>> >>> -- >>> Regards, >>> Cordialement, >>> Emmanuel L�charny >>> www.iktek.com >>> >>> >> >> >> >> > -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
