Skip to content
This repository has been archived by the owner on Jul 1, 2022. It is now read-only.

Commit

Permalink
Merge pull request #20 from InfoSec812/Issue-19-_-Fix_README_about_pr…
Browse files Browse the repository at this point in the history
…operties

Update README to reflect correct names for properties
  • Loading branch information
InfoSec812 authored May 9, 2019
2 parents a9f3144 + 5191e3d commit 7008be9
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,14 +43,14 @@ Go to the login form, a new button "Log in with Google" allow users to connect t
## General Configuration ##

Property | Description | Default value
---------| ----------- | -------------
sonar.auth.google.allowUsersToSignUp|Allow new users to authenticate. When set to 'false', only existing users will be able to authenticate to the server|true
sonar.auth.google.clientId.secured|Consumer Key provided by Google when registering the consumer|None
sonar.auth.google.clientSecret.secured|Consumer password provided by Google when registering the consumer|None
sonar.auth.google.enabled|Enable Google users to login. Value is ignored if consumer Key and Secret are not defined|false
sonar.auth.google.loginStrategy|When the login strategy is set to 'Unique', the user's login will be auto-generated the first time so that it is unique. When the login strategy is set to 'Same as Google login', the user's login will be the Google login. This last strategy allows, when changing the authentication provider, to keep existing users (if logins from new provider are the same than Google)|Unique
sonar.auth.google.limitOauthDomain|When set with a GApps domain, only allow users from that domain to authenticate|None
Property | Description | Default value
-------------------------------------------| ----------- | -------------
sonar.auth.googleoauth.allowUsersToSignUp |Allow new users to authenticate. When set to 'false', only existing users will be able to authenticate to the server|true
sonar.auth.googleoauth.clientId.secured |Consumer Key provided by Google when registering the consumer|None
sonar.auth.googleoauth.clientSecret.secured|Consumer password provided by Google when registering the consumer|None
sonar.auth.googleoauth.enabled |Enable Google users to login. Value is ignored if consumer Key and Secret are not defined|false
sonar.auth.googleoauth.loginStrategy |When the login strategy is set to 'Unique', the user's login will be auto-generated the first time so that it is unique. When the login strategy is set to 'Same as Google login', the user's login will be the Google login. This last strategy allows, when changing the authentication provider, to keep existing users (if logins from new provider are the same than Google)|Unique
sonar.auth.googleoauth.limitOauthDomain |When set with a GApps domain, only allow users from that domain to authenticate|None



Expand Down

0 comments on commit 7008be9

Please sign in to comment.