
Authenticating with Google Sign-In
Security Requirements and Controls
Change identity providers
permission
Step-by-step instructions for implementing Google Sign-In authentication in LogScale, including the creation of a Google Developer Console project, OAuth client ID setup, and configuration of authorized redirect URIs. The guide also covers essential security requirements and the necessary environment variables needed to enable Google authentication, with options for HTTP proxy settings and automatic user creation upon successful login.
Detailed setup instructions can be found in the Integrating Google Sign-In into your web app Google page.
Create a Project from the Google Developer Console,
Create an
OAuth Client ID
on the Credentials Page,Add an
Authorized redirect URI
:%PUBLIC_URL%/auth/google
where
%PUBLIC_URL%
is the same value as LogScale is configured with. This can behttp://localhost:8080/auth/google
during development. Login will fail if theredirect_uri
is not set correctly.Once your app is created you can configure LogScale to authenticate with Google, like this:
iniAUTHENTICATION_METHOD=oauth PUBLIC_URL=$YOUR_SERVERS_BASE_URL GOOGLE_OAUTH_CLIENT_ID=$CLIENT_ID #The client_id from your Google OAuth App GOOGLE_OAUTH_CLIENT_SECRET=$CLIENT_SECRET The #client_secret your Google OAuth App AUTO_CREATE_USER_ON_SUCCESSFUL_LOGIN=true # default is false
To have calls to the token endpoint for Google use the cluster's HTTP proxy settings, add the
GOOGLE_OAUTH_USE_HTTP_PROXY
configuration and set the value to true.Read more about Configuration Variables.