Hi, This is exactly what happens: I can make login with sAMAccountName working, but than groups will brake. The change I have in mind is to add one more parameter in config file to indicate property from LDAP to be used for login.
Anton -----Original Message----- From: Thomas Draier [mailto:[EMAIL PROTECTED] Sent: Monday, July 26, 2004 4:59 AM To: [EMAIL PROTECTED] Subject: Re: AD as LDAP provider hi anton, concerning the login with samAccountName, there's a problem with the current release but that has been fixed in the latest version on cvs. with the release you can still use the sAMAccountName attribute as an identifier, but that will lead to misfonctioning ldap groups (if you are using them). is that your problem ? what kind of change you are thinking about ? thomas Le 23 juil. 04, � 17:33, Anton Baranchuk a �crit : > Hi, > > Sorry for the delay. I finally found some time to get my changes in > order. > The files I am supplying are from the latest release. I had some > problems > using latest version from CVS. I did apply my changes to the latest > version, > but I haven't tested it (they are named as file.java_latest). > > I am not sure about one thing : shell I call invalidatePublicCtx() > once I > catch the PartialResultException? > > The other problem I am facing is the login: Our customers used to > login with > their Windows login name (sAMAccountName) -- that schema is not > supported by > current LDAP implementation. Once again I can make the change or wait > if you > are doing any work in that direction. > > Thank you. > Anton. > > -----Original Message----- > From: PELTIER Olivier [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 21, 2004 9:19 AM > To: [EMAIL PROTECTED] > Subject: RE: AD as LDAP provider > > > Hello, > > I'm currently working for this "another customer". > This referral error would be fixed soon I think. > > Regards. > > -----Original Message----- > From: St�phane Croisier [mailto:[EMAIL PROTECTED] > Sent: 21 July 2004 15:07 > To: [EMAIL PROTECTED] > Subject: RE: AD as LDAP provider > > > No, that's the right place. > > We were only waiting for some news from another customer who is also > adding > some new code for AD this week before answering to your points. On our > side > we are not AD experts and most of our customers are using standard LDAP > servers so it is sometimes quite difficult for us to answer to some > specific AD issues. > > But if you have some patches to submit, please feel free to post them > here > (or directly to [EMAIL PROTECTED]). We will review them or directly commit > them > in the CVS. > > Thanks for your patience, > St�phane > > At 14:50 21/07/2004, you 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. > > > > <JahiaGroupManagerLDAPProvider.java_latest><JahiaUserManagerLDAPProvide > r.java_latest><JahiaUserManagerLDAPProvider.java><JahiaGroupManagerLDAP > Provider.java>
