| commit | 32a93b1ae3c990d6b4a4c86c4012d3d13ac5332a | [log] [tgz] |
|---|---|---|
| author | Dag Bertelsen <dag.lennart.bertelsen@storebrand.no> | Tue Nov 17 07:21:52 2020 +0100 |
| committer | David Ostrovsky <david@ostrovsky.org> | Fri Jan 08 20:19:21 2021 +0100 |
| tree | d4428cefa60a539436c2f91a1f32055ae69f3f4c | |
| parent | ae0a0a1f27a1e546145c519504fc2dbed56d17af [diff] |
Validate the tokens issued from Azure * If a non-default tenant is used office 365 will now verify the token is issued by the tenant we are set to use. * All incoming tokens will be validated that they have set the same client_id that gerrit is set to use. Change-Id: I81e242c50ffd62e739e75a8c3a93d331049934a2
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