Howdy all, I'm setting up Koha for a client. They have an existing LDAP directory for user account authorisation, and want to use that for Koha's borrowers and administrators. There is documentation on making custom LDAP mappings, but I'm not sure what LDAP schemas are *needed* by Koha. What more is necessary beyond the common ‘person’, ‘posixAccount’, ‘inetOrgPerson’? -- \ “I watched the Indy 500, and I was thinking that if they left | `\ earlier they wouldn't have to go so fast.” —Steven Wright | _o__) | Ben Finney
Ben -- No particular schema is required by Koha. Each integration will depend entirely on what data the client Koha wants and what the LDAP server available presents. See the perldoc from C4::Auth_with_ldap for more info. The slides from my KohaCon presentation on LDAP may also be usefule, and are posted here: http://wiki.koha.org/lib/exe/fetch.php?media=kohacon_ldap.pdf They describe Koha fields that are considered "required", but also different levels of "requirement" for mapping data. -- Joe Atzberger LibLime - Open Source Library Solutions On Mon, May 4, 2009 at 8:52 PM, Ben Finney <ben+koha@benfinney.id.au<ben%2Bkoha@benfinney.id.au>
wrote:
Howdy all,
I'm setting up Koha for a client. They have an existing LDAP directory for user account authorisation, and want to use that for Koha's borrowers and administrators.
There is documentation on making custom LDAP mappings, but I'm not sure what LDAP schemas are *needed* by Koha. What more is necessary beyond the common ‘person’, ‘posixAccount’, ‘inetOrgPerson’?
-- \ “I watched the Indy 500, and I was thinking that if they left | `\ earlier they wouldn't have to go so fast.” —Steven Wright | _o__) | Ben Finney
Joe Atzberger <ohiocore@gmail.com> writes:
The slides from my KohaCon presentation on LDAP may also be usefule, and are posted here: http://wiki.koha.org/lib/exe/fetch.php?media=kohacon_ldap.pdf
This is useful, thank you.
They describe Koha fields that are considered "required", but also different levels of "requirement" for mapping data.
The slides make reference to required fields including “password”, and the “Required by login” slide has the following: password: * branchcode * categorycode I don't know what this is trying to tell me. How do I get Koha to authenticate each user by using LDAP's authentication database? (I hope the answer isn't “use the branchcode as the password”, as the above slide seems to suggest.) -- \ “I must say that I find television very educational. The minute | `\ somebody turns it on, I go to the library and read a book.” | _o__) —Groucho Marx | Ben Finney
participants (2)
-
Ben Finney -
Joe Atzberger