<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19046"></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Tom,</DIV>
<DIV> </DIV>
<DIV>As I understand it:</DIV>
<DIV>The Koha LDAP authentication mechanism copies user information from the LDAP tree to the local SQL database on the Koha server in order to create "user" accounts.</DIV>
<DIV>I believe one of the minimum requirements to create a Koha "user" account is a password.</DIV>
<DIV>
<DIV>Because of Koha's requirements for creating users, I don't think you will be able to populate the necessary fields to allow for users logins, without populating a password field.</DIV></DIV>
<DIV>Last time I dealt with them, passwords were hashed with MD5, and no clear text password were saved on the Koha system.</DIV>
<DIV> </DIV>
<DIV>-Scott</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><BR><BR>>>> Tom Hanstra<tom@nd.edu> 10/4/2011 9:56 AM >>><BR>We now have LDAP working to authenticate on logins. But we have also <BR>noticed that Koha stores that same password locally. Is there a <BR>configurable switch that I have not yet found which will keep LDAP <BR>connected logins from local storage?<BR><BR>Thanks,<BR>Tom<BR><BR>-- <BR><BR><BR>-----------------------------------------------------------------------------<BR> Tom Hanstra Systems Administrator<BR> Hesburgh Libraries of Notre Dame Phone: (574)631-4686<BR> 213 Hesburgh Library Email: tom@nd.edu<BR> Notre Dame, IN 46556<BR><BR> Every day, from here to there, funny things are everywhere.<BR> Dr. Seuss<BR>-----------------------------------------------------------------------------<BR><BR>_______________________________________________<BR>Koha mailing list <A href="http://koha-community.org">http://koha-community.org</A><BR>Koha@lists.katipo.co.nz<BR><A href="http://lists.katipo.co.nz/mailman/listinfo/koha">http://lists.katipo.co.nz/mailman/listinfo/koha</A><BR><BR></DIV></BODY></HTML>