| commit | 8d467e99457466c71eb0ca9e661dd433f03a0123 | [log] [tgz] |
|---|---|---|
| author | David Ostrovsky <david@ostrovsky.org> | Sun Apr 30 11:04:29 2023 +0200 |
| committer | David Ostrovsky <david.ostrovsky@gmail.com> | Sun May 07 07:56:22 2023 +0000 |
| tree | 5cc339dd797854a4cd86ba22173174338ec34f18 | |
| parent | 4bae1d7acc87f7dc1deca3813638bbc07ed5747f [diff] |
Keycloak OAuth2 provider: adapt endpoint URL to Quarkus runtime Starting from Keycloak release v17, the runtime was migrated to Quarkus. As the consequence, the "/auth" prefix was removed from the default context path. Romove the "/auth" prefix from endpoint URLs and mention in the documentation how to restore previous behaviour for backwards compatibility with legacy Keycloak releases. [1]: https://www.keycloak.org/migration/migrating-to-quarkus Change-Id: I8eef636b8104b6112b44692061621968f9ce6b15
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