External authentication provider for Sonarqube using Google OAuth2 / OpenID Connect
This project is a port of the existing project sonar-auth-github.
It maintains the same project structure, and I attempted to make only those changes necessary.
The directory diffs contains the file-by-file diffs between sonar-auth-github and sonar-auth-google as of Feb 13, 2016. These diffs won't be updated, and are intended to provide historical context as well as attribution to the original authors.
In terms of tecnhology stack, the main change is an updated version of scribe-java, from 2.1.0 to 2.3.0.
In terms of functional differences, there are two changes:
- the
loginStrategyoption value ofUniqueis not supported - the default value for option
allowUsersToSignUpisfalse
The GitHub plugin has a loginStrategy option setting of Unique which will generate a unique value for the Sonar user login ID iff user creation is allowed (option sonar.auth.github.allowUsersToSignUp=true) and the user is not already provisioned in Sonarqube.
Since Google authentication is (globally) authenticating a user's email address, this address is by definintion unique. This also means that in order for a user to be able to authenticate with Google, their login ID must be set to their Google email address. This can be safely updated for any existing Sonarqube users for whom you wish to enable Google authentication.
The other functional change is that the default value for option sonar.auth.google.allowUsersToSignUp is false. If you want anyone with a Google account to be able to automatically create an account on your Sonarqube system you should set this to true. Note that with the default setting, you must explicitly create a user account in Sonarqube with the Login value set to the email address used for Google authentication. When creating an account you must also set the Name of the user and create a password. If you only want this user to be able to authenticate with Google, create a highly complex random password and don't record it anywhere. Also note that when logging in with Google, the Name field will be updated with the name provided by Google authentication each time the user is authenticated. If the user updates their name in their Google account, this change will be reflected in Sonar.
When configuring the Sonarqube plugin you must supply the OAuth client ID and client secret using options sonar.auth.google.clientId and sonar.auth.google.clientSecret.
Basic instructions for setting up OAuth support for Google can be found here.
Note that if you have a Google Apps for Work account it is possible to restrict authentication of users to only those who belong to your domain(s). This is not done be default however, so by default any Google account holder can be authenticated.
Restricting authentication only to members of your Google Apps for Work domain(s) would allow the sonar.auth.google.allowUsersToSignUp option to be more safely enabled.