Rev 432 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
Rev 432 | Rev 433 | ||
---|---|---|---|
Line 30... | Line 30... | ||
30 | 30 | ||
31 | OIDplus::baseConfig()->setValue('GOOGLE_OAUTH2_ENABLED', true); |
31 | OIDplus::baseConfig()->setValue('GOOGLE_OAUTH2_ENABLED', true); |
32 | OIDplus::baseConfig()->setValue('GOOGLE_OAUTH2_CLIENT_ID', '..............apps.googleusercontent.com'); |
32 | OIDplus::baseConfig()->setValue('GOOGLE_OAUTH2_CLIENT_ID', '..............apps.googleusercontent.com'); |
33 | OIDplus::baseConfig()->setValue('GOOGLE_OAUTH2_CLIENT_SECRET', '.............'); |
33 | OIDplus::baseConfig()->setValue('GOOGLE_OAUTH2_CLIENT_SECRET', '.............'); |
34 | 34 | ||
- | 35 | (6) You might want to include a document in userdata/resources/ where you explain to your |
|
- | 36 | users that clicking the "Login using Google" link will redirect the user to |
|
- | 37 | Google in order to perform a login. During this login, Google will send the email address and |
|
- | 38 | the personal name of the user to OIDplus - nothing else. |
|
- | 39 | Note that the Google consent-screen will also have a privacy statement by Google. |