Bazel: switch oauth BUILD to native ext_deps support Use native `ext_deps` support in `gerrit_plugin()` and `gerrit_plugin_tests()` in the oauth plugin BUILD file. Declare external dependencies as Maven coordinates instead of generated Bazel labels, and share common test dependencies through `EXT_DEPS`. This removes repeated `@oauth_plugin_deps//...` labels, avoids explicit test target naming and manual `:oauth__plugin` wiring, and drops the separate call to `gerrit_plugin_dependency_tests()`. Change-Id: Ib076fc310be6b0b75b17dff7d80e25defdd2b728
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 with Bazel, install Bazel and run the following:
git clone https://gerrit.googlesource.com/plugins/oauth cd oauth && bazel build oauth
Copy the bazel-bin/oauth.jar to $gerrit_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