| commit | 024c1d9e625b783b2d2cde6c2882188aeda68736 | [log] [tgz] |
|---|---|---|
| author | Joe Shannon <joe.shannon@diamond.ac.uk> | Wed Sep 14 16:50:51 2022 +0100 |
| committer | Joe Shannon <joe.shannon@diamond.ac.uk> | Fri Sep 16 15:28:36 2022 +0100 |
| tree | 8fe8373801b27edb689e17850c9abfd6cd107eeb | |
| parent | f9bef7476bc99f7b1dc3fe2d52ec95cd7ac571dc [diff] |
Allow JSON token extractor to be used with CAS Add config boolean to use JSON token extraction rather than the regex based extractor for plain text responses. Support for JSON token responses was added in CAS v6.1.0: https://github.com/apereo/cas/pull/1645 Support for plain text seems to have been removed in the same release by this commit: https://github.com/apereo/cas/commit/c9b555386f7e165d98d6616b4294 Default behaviour unchanged to continue to support CAS v5 users. Bug: Issue 16232 Change-Id: I15f195001e5ee823f3832388b23c6b2f2dbb3cd4
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