Re: [viewvc-users] Can ViewVC be configured for LDAP and multiple repositories?

Nassani, Joseph - ES/EW wrote:
> I’m attempting to configure viewvc on my server which is hosting 3
> repositories whose authentication is controlled via LDAP (Microsoft
> Active Directory).  I’d like viewvc to understand LDAP authentication
> and to understand that I have 3 separate repositories which have
> different security requirements – folks from one should not be able to
> read the data from another.
>  
> Can this be done?  If so any assistance would be very much appreciated.

ViewVC 1.1.0+ will accept from Apache whatever username Apache provides it,
and can be configured to use that username to test for path-based
authorization privileges against the likes of a Subversion authorization file.

So, if you aren't yet running ViewVC 1.1.0 or better, then, "No."

Assuming we're past that, though, you should be able to tell Apache that all
ViewVC access must pass through your LDAP authn mechanism easily enough.  By
this, I mean "as easily as you'd tell Apache to require LDAP authn for any
other thing on your system".  I don't have personal experience in this type
of configuration, but I suspect we're talking about a <Location> block for
your ViewVC URIs and a bunch of LDAP-related Apache directives inside there.

As long as Apache then communicates to ViewVC the LDAP-authenticated name of
the user via the standard way of doing so for CGI-based applications, and as
long as you are using a ViewVC authz plugin that cares about usernames (such
as the svnauthz one), ViewVC should be able to use that username in its
authorization checks.

-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2379566

To unsubscribe from this discussion, e-mail: [[email protected]].

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkp3AJ8ACgkQokEGqRcG/W4kYgCgyHImHoz2v9USKBlY2Bmcf3v1
GuUAn0jg1YEHuXEF83j3gFqKJCwUGWOd
=X9og
-----END PGP SIGNATURE-----