🚀 go-pugleaf

Hello,

For your problem you have an action in progress at www.dmtf.org . This
action is a common model for devices, people, IPSEC, QoS, ...

Thus for architecture, I think you have to built a three parts achitecture
with a application server between clients and LDAP servers. Another solution
is meta-directory. Following some providers : Microsoft, Novell,
Critical-Path, ...

Best Regards

Chris.




"Want to Know Eh?" <want@2no.eh> a �crit dans le message news:
pan.2002.11.12.16.25.00.334711@2no.eh...
> I have been charged with designing an ldap schema that is goign to support
> "plugging-in" to the systems of several of our offices worldwide.
>
> While this in itself would not be difficult, the issue arises that several
> of these offices are on different systems and use different tools (ie.
> head office is on unux/NIS, one office uses windows and NDS, another
Win/AD,
> yet another Lotus etc.) to administer their users, manage them etc.
>
> My trouble is figuring out a schema that will provide a common "coverage"
> of all these where users and their authorizations (services/groups) can be
> centralized and handled in a trouble free manner with openldap servers
> worldwide and still allow local offices autonomy while making their
changes
> available worldwide as well as providing an authentication and login
> mechanism and drop in security replacement for NIS.
>
> Even after quite a bit of reading and some expert advice I still feel like
> we're not there. I'd be interested in what other people in this position
> have done or pointers to better resources on the Net that might be of help
> (or some better books).
>
> looking forward to discussing this issue...
> ciao!
> D.
>