From: "Shawn O. Pearce" <spearce@spearce.org>
To: Pedro Lemos <pedrolemos454@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: Git Server Authentication & Management
Date: Mon, 4 Jan 2010 08:33:16 -0800 [thread overview]
Message-ID: <20100104163316.GC22872@spearce.org> (raw)
In-Reply-To: <1a710981001040827q23f61bdew8db1ae76d5bfb855@mail.gmail.com>
Pedro Lemos <pedrolemos454@gmail.com> wrote:
> I'm relatively new to Git.
> At the moment I'm trying to understand if it will be possible to:
>
> 1 - configure a central server (server A) to host all my git repositories.
> 2 - also I would like to configure access to those Git repositories in
> order to use authentication:
> - using LDAP;
> - using MS Active Directory;
You might want to look at Gerrit Code Review [1]. It has
out-of-the-box support for integration with Active Directory.
[1] http://code.google.com/p/gerrit/
> 3 - Moreover, I would like to know if is there any administration
> interface to use within git repositories?
Gerrit Code Review uses a web based administration interface, though
with an LDAP/Active Directory configuration access controls will
most likely be managed in the directory server by user membership
to groups.
> 4 - And to close this email, I need a way to manage access permissions
> over the server repositories. Such as:
> - read-write, read-only, or no access at all;
> - deletes-allowed, renames-allowed, tags allowed;
Yup, Gerrit Code Review can do that.
It also can be used as a code review system. :-) But if you don't
want to use the code review features, you can just grant out the
Push Branch +1 (or +2 or +3) permission to allow pushing to a branch.
A different, but much more popular choice is gitosis [2], but that
doesn't use LDAP for user authentication and access management.
It uses its own SSH key repository. To be fair, Gerrit Code Review
also uses its own SSH key repository... but users can manage their
keys individually through the web interface, which is authenticated
by LDAP.
[2] http://eagain.net/gitweb/?p=gitosis.git
--
Shawn.
prev parent reply other threads:[~2010-01-04 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 16:27 Git Server Authentication & Management Pedro Lemos
2010-01-04 16:33 ` Shawn O. Pearce [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100104163316.GC22872@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=pedrolemos454@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).