[Date Prev][Date Next]
Re: central database on one server, "dislocated" servers in many cities
Through use of replication in slapd(8), you can do 1) through 4).
5) is not possible in slapd(8) as the "central" server would
be the master server in the outlined scenario.
At 01:07 AM 10/26/2004, Tomasz Chmielewski wrote:
>I'm rather new to OpenLDAP, recently I make it work with Samba.
>What should I look for / read, if I want to do the following:
>1) we have a couple of office branches (say 20) located in different
>parts of the country, employees travel often between these branches
>2) each branch office is connected to internet using rather slow /
>3) the task is to add / delete users on one central machine
>4) then, when user is added / deleted, all the changes are "uploaded" to
>each branch office - so that authentication there (in branch office)
>could be done fast (no need to check on the central server), and
>wouldn't be prone to network failures (when link to the central server
>5) moreover, in each branch, clients should be able to change their passwords, and Samba should be able to add machines to the database automatically. These changes should be added to the local machine (to save time on a tight bandwidth, prevent failures due to broken link etc.), which would then be transferred to the central server, and from there, to the rest of the branch offices.
>What should I look for? Replication? LDAP proxy cache? Anything else?