<div dir="ltr"><br><br><div class="gmail_quote">On Tue, Oct 7, 2008 at 8:09 AM, Scott Owen <span dir="ltr"><<a href="mailto:sowen@edzone.net">sowen@edzone.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br>
<br>
First: Please forgive my ignorance.....I'm not a programmer....and I may<br>
be biting off more than I can chew ......<br>
<br>
Is there a (easy) way to pass authentication information to Koha ??<br>
Or.....a way to have/make Koha generate a session cookie based on<br>
external information? Or maybe change the way cookies are generated/issued?<br>
<br>
I've been trying to figure out a way for my users (k-12 students) to use<br>
the same login/password in Koha as they do everywhere else.<br>
We use Novell NDS/LDAP as our main authentication mechanism.<br>
<br>
I have a basic PHP/Perl login script (<br>
<a href="http://www.novell.com/coolsolutions/tools/14122.html" target="_blank">http://www.novell.com/coolsolutions/tools/14122.html</a>) that can return<br>
basic information like:<br>
******************************<br>
Bind result is: 1<br>
1 entries returned<br>
Login Successful - Welcome Test Student<br>
Here you could add sessions or cookies to verify the person has logged<br>
in with the corect UserName and Password.<br>
<br>
*Title:*<br>
*Sur Name:* Student<br>
*Given Name:* Test<br>
*E-Mail:*<br>
<br>
<br>
********************************<br>
<br>
I have tried using the Auth_With_ldap.pm but have been unable to get it<br>
to work :-( and decided to try this approach instead.<br>
<br>
Thanks for any help.<br>
<br>
-Scott Owen<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Koha mailing list<br>
<a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
</blockquote></div><br>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. :)<br clear="all"><br>-- <br>Jesse Weaver<br>
Software Developer, LibLime<br>
</div>