Unnamed repository; edit this file 'description' to name the repository.
git clone git@jamesshield.xyz:repos/loginsrv.git
Log | Files | Refs | README | LICENSE

commit 0209158f5d839bcaf8671bad7bbe4661407f7018
parent 15fde6118a9a75dafcdf21e3c5b965f50ec434da
Author: Sebastian Mancke <s.mancke@tarent.de>
Date:   Fri, 17 Nov 2017 16:54:38 +0100

Merge pull request #59 from dobegor/patch-1

Update README.md to note about People API for Google
MREADME.md | 6+++++-
1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md @@ -241,7 +241,7 @@ The Oauth Web Flow (aka 3-leged-Oauth flow) is also supported. Currently the following oauth Provider is supported: * github -* google +* google (see a note below) * bitbucket An Oauth Provider supports the following parameters: @@ -262,6 +262,10 @@ if loginsrv is routed through a reverse proxy, if the headers `X-Forwarded-Host` $ docker run -p 80:80 tarent/loginsrv -github client_id=xxx,client_secret=yyy ``` +### Note for Google's OAuth 2 +When configuring OAuth 2 credentials in Google Cloud Console, don't forget to enable corresponding API's. +For example, for `scope=https://www.googleapis.com/auth/userinfo.profile` [Google People API](https://console.cloud.google.com/apis/library/people.googleapis.com/) must be enabled for your project. Keep in mind that it usually takes a few minutes for this setting to take effect. + ## Templating A custom template can be supplied by the parameter `template`.