[Koha-bugs] [Bug 10842] Allow for new type of LDAP authentication - Further Enhancement

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10842

--- Comment #3 from Martin Renvoize <martin.renvoize at ptfs-europe.com> ---
I Suppose I should probably put in a test plan, now I've got my head around it
myself!

If you've found this bug, then most likely you've found that your LDAP Server
requires the setup as explained in the first post, or your just grabbing at
straws?

To enable this method you'll need to enable auth_by_bind and also include a
user and password in your ldap configuration xml for koha as in the below
example.

 <useldapserver>1</useldapserver>                                       <!--
see C4::Auth_with_ldap for extra configs you must add if you want to turn this
on -->
 <ldapserver id="ldapserver">                                           
    <hostname>ldap://yourldapserver.com:389</hostname>                  <!--
LDAP Server hostname -->
    <base>DC=yourldapserver,DC=com</base>                               <!--
LDAP Server Base     -->
    <user>CN=kohabindaccount</user>                                     <!--
DN, if not anonymous -->
    <pass>gobbledegoop</pass>                                           <!--
password, if not anonymous -->
    <replicate>0</replicate>                                            <!--
add new users from LDAP to Koha database -->
    <update>0</update>                                                  <!--
update existing users in Koha database -->
    <auth_by_bind>1</auth_by_bind>                                      <!--
set to 1 to authenticate by binding instead of password comparison, e.g., to
use Active Directory -->
    <mapping>                                                           <!--
match koha SQL field names to your LDAP record field names -->
        <firstname is="givenName"> </firstname>
        <surname is="sn"> </surname> -->
        <address is=""> </address> -->
        <city is=""> </city> -->
        <userid is="samAccountName"></userid>
        <password is=""           ></password>
        <categorycode is=""   >TEMP</categorycode> -->
        <email is=""></email> -->
        <dateenrolled is="">2011-07-12</dateenrolled> -->
        <dateexpiry is="">2012-07-12</dateexpiry> -->
    </mapping>
 </ldapserver>

If it didn't authenticate before, but does now then the patch has fixed your
issue ;)

-- 
You are receiving this mail because:
You are watching all bug changes.