e9e046a4b3
OAuth2 support was only implemented for the web UI so far but not for Git-over-HTTP communication. This patch adds a mechanism similiar to that supported by Github, where Git clients may send OAuth2 access tokens instead of passwords in a Basic authentication header [1]. Received access tokens will be verified by means of an OAuthLoginProvider, which is a new extension point. The OAuth2 protocol does not specify a mechanism for how to verify access tokens, so there is no default implementation for the OAuthLoginProvider interface, but a plugin must provide a suitable implementation. In order to enable OAuth2 authentication for Git-over-HTTP the configuration option auth.type must be set to OAUTH and auth.gitBasicAuth must be set to true. The parameter auth.gitOAuthProvider defines the default OAuthLoginProvider to use in case multiple OAuthLoginProvider implementations are installed and it cannot be deduced from the request, which OAuth provider to address. An OAuthLoginProvider implementation may also support HTTP Basic authentication with passwords instead of access tokens, if the OAuth2 backend supports the Resource Owner Password Credentials Grant authentication flow [2] or some other API for verifying password credentials. For that reason the second parameter of the OAuthLoginProvider interface is called "secret" instead of "accessToken". An example implementation for the OAuthLoginProvider extension point will be contributed to the cfoauth plugin. [1] https://developer.github.com/v3/auth/#basic-authentication [2] https://tools.ietf.org/html/rfc6749#section-4.3 Change-Id: I0f00599dce38a806fd3e21758ea9e2cab49ce57f Signed-off-by: Michael Ochmann <michael.ochmann@sap.com>
Gerrit Code Review
Gerrit is a code review and project management tool for Git based projects.
Objective
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
Documentation
For information about how to install and use Gerrit, refer to the documentation.
Source
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Reporting bugs
Please report bugs on the issue tracker.
Contribute
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
Getting in contact
The IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
The Developer Mailing list is repo-discuss on Google Groups.
License
Gerrit is provided under the Apache License 2.0.
Build
Install Buck and run the following:
git clone --recursive https://gerrit.googlesource.com/gerrit
cd gerrit && buck build release
Install binary packages (Deb/Rpm)
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.
Events
- November 7-8 2015: Gerrit User Conference, Mountain View. (Register).
- November 9-13 2015: Gerrit Hackathon, Mountain View. (Invitation Only).
- March 2016: Gerrit Hackathon, Berlin. (Details to be confirmed).