[Date Prev][Date Next]
RFT0001 : Request For Thoughts
- To: <firstname.lastname@example.org>
- Subject: RFT0001 : Request For Thoughts
- From: "Christopher Barry" <email@example.com>
- Date: Mon, 22 Sep 2008 12:06:50 -0500
- Content-class: urn:content-classes:message
- Thread-index: Ackc1Zprj+9bGuULQeiL6wqAqjGBDA==
- Thread-topic: RFT0001 : Request For Thoughts
If this post here is in poor taste, please pardon my interruption. It's
just that I figured those here would have a high probability of trying
to do as I am trying to do.
I'm a debian-head from the early 90's, but I'm new to OpenLDAP, and this
is my first post here. I'm about halfway done with Mastering OpenLDAP,
and I've been lurking here for a month or so, trying to understand how
things work, and looking for questions like mine. I also just read
Kerberos, the definitive guide as a primer into understanding how my
team can make everyone 'Just Get Along(tm)' in a multi-platform global
enterprise, while leveraging open source projects.
* We're exploring ways in which we can have a single user/group database
for everything, everywhere in our domain.
* Additionally, we want as 'SSO' an environment as possible.
* We also want to keep, and even extend all the other NIS functionality
we use today - only without the NIS limitations.
* We also need to be able to phase it in, or even have it overlap with
our current situation for a period, so it's not an all-or-nothing kind
The Parts Bin:
There's a bunch of parts around, and they all kind of fit together, but
to my current understanding anyway, seem to create a few different
incomplete solutions, such as:
* Samba/Winbind/Kerberos (possibly backed by OpenLDAP)
* OpenLDAP/Kerberos with trusts to AD
* AD using 2003R2 and possibly custom schema modifications if required.
My question really is what are others doing to solve this type of
problem? Architecturally, what is the best approach given the above
Thanks to all for your thoughts and insight on this,