Hi Kevin! Thanks for your information about the wrong LDaP.pm and sorry for the trouble. What OTRS version are your runing? Would you open a bug report for this problem on http://bugs.otrs.org please? Best regards, Christian On Do, Mai 26, 2005 at 02:39:37 -0700, Kevin Kasner wrote:

Update... I fixed it - Sort of. The LDAP.pm in the CustomerAuth directory listed its' revision as 1.8 and the LDAP.pm in the Auth directory listed its' revision as 1.13, so... I copied the newer LDAP.pm to the CustomerAuth directory, edited the package name to ...tem::CustomerAuth::LD... and added C. to the start of the text in the log lines so I could tell that I was using the new LDAP.pm and voila! I could log in as a user.

Next I updated the 'get ldap preferences' section to get the settings from Customer::AuthModule instead of AuthModule and it broke again...

Final Update: hehe. this is almost emabarrasing. I deleted the CutomerAuth settings completely from my config.pm, re-copied them from the Auth section, added Customer:: to the front of each of them and put back the original (1.08) LDAP.pm and everything works...

I guess the lesson is check, double check, then check again before posting...

Thanks!

On 5/26/05, Kevin Kasner wrote:

...

Hi All, Love OTRS so far (and my CIO is going to love it more!)...Have it running on SuSe 9.3 w/ MySQL and Apache2.

I have LDAP/AD working perfeclty (as far as I can tell ) for the Agents and for the Customer Backend, but I'm running into trouble getting it to work for the Customer Authentication... - for example, I can login as myself as an agent. And then look myself up in the Customer User Management by first name and have the system return all of the kevins from my AD...

I'm using exactly the same host, BaseDN, SearchUserDN/Pw, and UID for all three sections in config.pm. (via copy/paste) and I'm not using the GroupDN attribute in any of them.

I've done some packet captures and I'm seeing some differences between the successful and failed LDAP connections:

Successful: I see a bind request from a specific port with the bind result going back to that same port. Then I see the Search request come from the same port and the search result is returned.

not Successful: I see a I see a bind request from a specific port with the bind result going back to that same port. Then I see the Search request come from a different port and the message returned is: "In Order to perform this operation a successful bind must be completed on the connection."

Any thoughts on what I should look at next would be greatly appreciated!

Thank you.

Kevin.

_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/

-- ((otrs.de)) :: OTRS GmbH :: Norsk-Data-Str. 1 :: 61352 Bad Homburg http://www.otrs.de/ :: Manage your communication!