On Tue, Nov 18, 2008 at 12:58 AM, Kurt Buff <[EMAIL PROTECTED]> wrote:
> They've gotten stuck on the idea that it can all be done through Cyrus
> SASL, ldap and svnserve, with nothing else on the box.
If they're so sure, why can't they provide you with the information
you need to do it?
Hmmm. I originally wrote that tongue-in-cheek, but it may be a
workable approach: They either have some good reason for thinking that
way, or they are working on incomplete information. If the former,
they can give you that information, which will presumably help you.
If the latter, you can point to that lack of basis *and* the
information you do have, and then find some diplomatic way of saying
"You're full of shit."
I don't know much of anything about Subversion/AD integration, but I
tried this Google:
http://www.google.com/search?q=svnserve+%22Active+Directory%22
which immediately led me to:
http://svnbook.red-bean.com/en/1.4/svn.serverconfig.choosing.html
which states:
If you need to integrate with existing identity systems
(LDAP, Active Directory, NTLM, X.509, etc.), then an
Apache-based server is your only real option.
Other Google hits re-enforce this. It sounds like svnserve with
only SASL basically means you're keeping your own authentication
database for svnserve -- no external integration possible. Some of
said Google hits do state that svnserve by itself (instead of going
through Apache) is a performance win, but for a business, I'd say
authentication is more important than speed.
-- Ben
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
