At 10:39 PM 12/20/2002 -0700, you wrote:
>
>> ldap = is it proven techology for this purpose?
>> 
>
>       LDAP is a general purpose thing now, you can really put anything in
>LDAP. LDAP from companies such as Sun (Sun ONE Directory Server) have
>extra plugins and if you don't mind using one of those the licensing is
>ultra cheap I think it was $1 for upto 100,000 licenses. It has some
>"plugins" to do some things like NT passwd syncs etc etc. It works with
>RH 7.2/7.3 I haven't tried it on 8.0 though.
>
>       So LDAP is quite a proven technology, by extension its the software
>that plugs in which you should question, SAMBA is quite reliable for
>this and with LDAP its quite portable. You will have to compile the
>SAMBA software for use as the RH one is not LDAP-aware or not compiled
>with LDAP switches.
>

Hi, i'm trying to use ldap as a back end and samba for user auth (before
completely moving all client to linux).
We have 4 site on different city, which also maintain by 4 admins. 
What is the 'correct' suffix for those 4 site? 
I'm thinking of 2 options :
1. dc=siteOne,dc=mydomain,dc=com
2. dn=mydomain,dc=com

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?

Tks.




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to