Hi Anton,
No, this is the correct place. I've been swamped with work recently, and changed email clients, so I didn't see that your question had not been replied too (and in these mailing lists answers are not guaranteed anyway, this is not a commercial support channel :)).
Anyway I am interested in your proposals, and I think the best way would be to send me modified versions of the classes you have changed, so that I can compare them with the existing implementation, and if they look non-disruptive I can commit them.
Also it might be interesting to do this modification in both providers, the group and the user provider, so you might want to look into that.
Regards, Serge Huber.
Anton Baranchuk wrote:
Was it wrong place to post my question? I would appreciate any input.
Thank you. Anton
-----Original Message----- From: Anton Baranchuk [mailto:[EMAIL PROTECTED] Sent: Monday, July 19, 2004 11:20 AM To: '[EMAIL PROTECTED]' Subject: AD as LDAP provider
Hi,
My company uses AD as a LDAP provider, and I am having certain problems with
it:
1. I need to set Context.REFERRAL environment variable for initial context
to "follow"
(default is "ignore"). Can you please add this as a configuration
parameter for LDAP config?
it is JahiaUserManagerLDAPProvider.connectToPublicDir and
JahiaGroupManagerLDAPProvider.connectToPublicDir methods. Actually I can submit the code, but I haven't figured out how that
works.
2. Because of our weird setup I have to process
javax.naming.PartialResultException and disregard it (This is happening every time with AD which sits on another sub
network to which your DNS can't resolve references)
Is it possible to incorporate that as an optional feature? I also
have sample code. Can submit it for review.
Thank you. Anton.
