At 11:10 AM 1/3/2003 -0800, you wrote: >On Fri, 2003-01-03 at 10:39, Beast wrote: >> Server design: >> all sites are connected using leased line, so problem in links should not >> interupt user in one site to authenticate(or modify their password) to >> their own ldap server, but all servers in all sites should be synch. >> >> What is the best design for that case? create one 'root' server (with all 4 >> server are 'children' of this svr) or create 4 independent server? > >OpenLDAP's multi-master replication support is currently experimental. >For you that means: > >If you build a single master system and replicate to the other three >offices, you'll be able to authenticate in the event of a link failure, >but you won't be able to modify the directory (change passwords).
That's what i'm thinking of. The root dn will be: "dn: dc=example,dc=com" ? > >If you build separate systems for each office, you'll be able to >authenticate and change passwords independent of any other office, but >none of the offices will know about each other's users. This seems good solution. what if in each server we define a referal? will user will know each other? root DN will be "dn: dc=site one, dc=example,dc=com" ? -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
