User manual

Chapter 13
Next we look at the file
ccl .properties
stored in the folder
/etc /koha -dev /etc/
zebradb /:
linux- 4yut: /usr/ share /kohaclone /misc /migration_tools # vi /etc /koha -dev/
etc /zebradb /ccl.properties
If we run a search on the index
Local -number,
we find an entry as follows:
Local- number 1 =12
sn Local- number
The index
Local -number
is present in both these files and we can use it in the Search
index field in matching rules.
More information and examples
For more information and examples on matching rules, refer to Koha community
documentation on this topic, available at:
http: / /koha- community.org/ documentation /3- 2- manual /x3735 #AEN4124.
Using LDAP with Koha
If your organization uses an LDAP (Lightweight Directory Access Protocol) server
for user authentication, it makes sense to configure Koha to integrate with it. This
way you don't have to maintain users and passwords in two places, the LDAP server
and in Koha.
This is how Koha works with LDAP:
When a user logs into Koha, the password entered by the user is verified
against the password maintained on the LDAP server.
We can configure Koha such that when a user logs in for the first time,
his /her patron category, branch, address, and other such information is
copied over into Koha.
We can configure Koha such that if a user's LDAP record is updated,
the updated information is copied over into Koha when the user next
logs into Koha.
We can map fields in the LDAP database to fields in Koha. This way we
can make sure LDAP data is copied into Koha correctly.
It is fairly simple to configure Koha to use LDAP; let us take a look at a general
example followed by the specific case of configuration for Microsoft Active Directory.
[249]