| commit | 90dfc1013b5586bc1be3eb07a0db17d73873c7b7 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Thu Jun 20 16:31:27 2013 +0100 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Fri Jun 21 18:56:37 2013 +0100 |
| tree | 8b7cc084453cd8b5b01e28aa5535f3afbe8ad6da | |
| parent | 395cbbeff5d2c6b4e92a710316a7cd33ecae4d26 [diff] |
GitHub OAuth2 implementation as Gerrit HTTP Auth. First integration point for allowing Gerrit to authenticate users through GitHub OAuth. It relies on the installation of the github-oauth Java library under the $GERRIT_SITE/lib in order filter all the HTTP requests through the GitHub OAuth 2.0 secure authentication. In order to configure the GitHub authentication you need to: - copy the github-oauth into $GERRIT_SITE/lib - copy the github-plugin into $GERRIT_SITE/plugins - run the Gerrit init steps by choosing HTTP Auth - set the GitHub parameters during the GitHub custom init step Change-Id: I0898994169fec0b477dc8944045ceba9526a4d9c
Integration between Gerrit and an external repository on GitHub.
Provides the basic integration points for working effectively with Gerrit as code-review tool for an existing repository hosted on GitHub:
Users can login to Gerrit using the same username and credentials in GitHub. Gerrit login points to GitHub for generating the SSO token to be used for the code-review authenticated session.
Existing GitHub repositories are automatically replicated to Gerrit for the purpose of performing code-review and pushing back changes once approved. Additionally to the standard Gerrit push replication, supports as well the ability to pull branches from remote GitHub repositories.
Hooks into the GitHub pull-request mechanism to automatically create a Change in Gerrit submitted for review.