commit | 1977f6fbaaa14f225d3dde72c2d3db4482da70de | [log] [tgz] |
---|---|---|
author | David Ostrovsky <david@ostrovsky.org> | Fri Feb 01 09:50:21 2019 +0100 |
committer | David Ostrovsky <david.ostrovsky@gmail.com> | Mon Feb 04 09:43:32 2019 +0000 |
tree | ce2c8c7b3a4b41ee652e8f7b4810a28bfc01766e | |
parent | 8dc84054bbd115fd470731f7daf923183e7ab4d1 [diff] |
GoogleOAuthService: Stop using deprecated Google+ userinfo endpoint The Google+ Sign-in feature is fully deprecated and is being shut down on March 7, 2019. This will be a progressive shutdown, with intermittent failures starting as early as January 28, 2019. Developers should migrate to the more comprehensive Google Sign-in authentication system. Switch to using OAuth2 userinfo endpoint: [1]. [1] https://developers.google.com/+/web/signin Change-Id: I01f8b5816e39226da4fde2dcf66cc43670d94c08
With this plugin Gerrit can use OAuth2 protocol for authentication. Supported OAuth providers:
See the Wiki what it can do for you.
Prebuilt binary artifacts are available on release page. Make sure to pick the right JAR for your Gerrit version.
To build the plugin, install Buck and run the following:
git clone --recursive https://github.com/davido/gerrit-oauth-provider.git cd gerrit-oauth-provider && buck build plugin
Copy the buck-out/gen/gerrit-oauth-provider.jar
to $gerit_site/plugins
and re-run init to configure it:
java -jar gerrit.war init -d <site> [...] *** OAuth Authentication Provider *** Use Bitbucket OAuth provider for Gerrit login ? [Y/n]? n Use Google OAuth provider for Gerrit login ? [Y/n]? Application client id : <client-id> Application client secret : confirm password : Link to OpenID accounts? [true]: Use GitHub OAuth provider for Gerrit login ? [Y/n]? n
Make sure to read the FAQ before reporting issues.
Apache License 2.0