Thanks for the response Jesse, "What specific problem are you having with Auth_with_ldap.pm?" Well......I'm really not sure.....(think maybe that's the problem?? :-) ).... I posted the problem previously on 10/1/2008 to this list.... titled "LDAP and 2.2.9 on Win32" (and got the standard response....."upgrade to 3.0 "...unfortunately...the upgrade path on the win32 platform seems to be on hold for now...) In a nutshell....I don't seem to get authenticated.....and I'm nor sure if I need to use a proxy user? or if I can use an anonymous bind? here is a repost of the previous message: ************************************************************* Issue: I'm trying to use LDAP authentication to avoid duplication of data entry (users/members). I've searched and found a few tid-bits regarding Koha and LDAP, but couldn't really find much solid info and/or any "how-to's" I've tried the basic renaming of Auth_with_ldap.pm....and adding my LDAP server info (IP and base user context), this gets me basically nowhere, and removes the user login/password prompt section from the Opac page.???? I assumed that this would do an anonymous bind, and then prompt for user credentials....this seems to to be incorrect. Do I need to enter a specific user somewhere? At this point the systems seem to at least see each other.... _Koha OPAC error log:_ Oct 01 10:07:37 2008] [error] [client 127.0.0.1] password combination at c:/usr/koha229/intranet/modules/C4/Auth.pm line 528. [Wed Oct 01 10:07:39 2008] [error] [client 127.0.0.1] LDAP Auth failed server not responding or wrong user [Wed Oct 01 10:07:39 2008] [error] [client 127.0.0.1] password combination at c:/usr/koha229/intranet/modules/C4/Auth.pm line 528. [Wed Oct 01 10:07:41 2008] [error] [client 127.0.0.1] LDAP Auth failed server not responding or wrong user [Wed Oct 01 10:07:41 2008] [error] [client 127.0.0.1] password combination at c:/usr/koha229/intranet/modules/C4/Auth.pm line 528. _ My LDAP servers eror log (10.1.1.192 is the IP of my Koha server):_ New cleartext connection 0xa7684b60 from 10.1.1.192:2182, monitor = 0x259, index = 1 Monitor 0x259 found connection 0xa7684b60 socket closed, err = -5871, 0 of 0 bytes read Monitor 0x259 initiating close for connection 0xa7684b60 Server closing connection 0xa7684b60, socket error = -5871 Connection 0xa7684b60 closed New cleartext connection 0xa7684b60 from 10.1.1.192:2186, monitor = 0x259, index = 1 Monitor 0x259 found connection 0xa7684b60 socket closed, err = -5871, 0 of 0 bytes read Monitor 0x259 initiating close for connection 0xa7684b60 Server closing connection 0xa7684b60, socket error = -5871 Connection 0xa7684b60 closed New cleartext connection 0xa7684b60 from 10.1.1.192:2189, monitor = 0x259, index = 1 Monitor 0x259 found connection 0xa7684b60 socket closed, err = -5871, 0 of 0 bytes read Monitor 0x259 initiating close for connection 0xa7684b60 Server closing connection 0xa7684b60, socket error = -5871 Connection 0xa7684b60 closed I can access the LDAP server via the Softerra LDAP browser with no issues. Does anyone have a working Auth.pm with LDAP that they could either send me, or cut/paste here? ****************************************************************** Jesse Weaver wrote:
On Tue, Oct 7, 2008 at 8:09 AM, Scott Owen <sowen@edzone.net <mailto:sowen@edzone.net>> wrote:
Hi all,
First: Please forgive my ignorance.....I'm not a programmer....and I may be biting off more than I can chew ......
Is there a (easy) way to pass authentication information to Koha ?? Or.....a way to have/make Koha generate a session cookie based on external information? Or maybe change the way cookies are generated/issued?
I've been trying to figure out a way for my users (k-12 students) to use the same login/password in Koha as they do everywhere else. We use Novell NDS/LDAP as our main authentication mechanism.
I have a basic PHP/Perl login script ( http://www.novell.com/coolsolutions/tools/14122.html) that can return basic information like: ****************************** Bind result is: 1 1 entries returned Login Successful - Welcome Test Student Here you could add sessions or cookies to verify the person has logged in with the corect UserName and Password.
*Title:* *Sur Name:* Student *Given Name:* Test *E-Mail:*
********************************
I have tried using the Auth_With_ldap.pm but have been unable to get it to work :-( and decided to try this approach instead.
Thanks for any help.
-Scott Owen
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> http://lists.katipo.co.nz/mailman/listinfo/koha
What specific problem are you having with Auth_with_ldap.pm? Figuring out the problem with that might be easier than hacking the main authentication code. :)
-- Jesse Weaver Software Developer, LibLime