2022-05-26 10:06:25 -05:00
---
aliases:
2022-12-09 10:36:04 -06:00
- ../../../auth/google/
2022-06-02 11:57:22 -05:00
description: Grafana OAuthentication Guide
2023-05-18 09:50:20 -05:00
title: Configure Google OAuth2 authentication
2022-06-02 11:57:22 -05:00
weight: 300
2022-05-26 10:06:25 -05:00
---
2018-09-06 05:11:56 -05:00
2022-06-02 11:57:22 -05:00
# Configure Google OAuth2 authentication
2018-09-06 05:11:56 -05:00
2020-06-24 08:46:31 -05:00
To enable Google OAuth2 you must register your application with Google. Google will generate a client ID and secret key for you to use.
2018-09-06 05:11:56 -05:00
## Create Google OAuth keys
First, you need to create a Google OAuth Client:
2020-02-20 03:16:25 -06:00
1. Go to https://console.developers.google.com/apis/credentials.
2020-10-01 11:45:05 -05:00
1. Click **Create Credentials** , then click **OAuth Client ID** in the drop-down menu
1. Enter the following:
2018-09-06 05:11:56 -05:00
- Application Type: Web Application
- Name: Grafana
2020-06-24 08:46:31 -05:00
- Authorized JavaScript Origins: https://grafana.mycompany.com
2018-09-06 05:11:56 -05:00
- Authorized Redirect URLs: https://grafana.mycompany.com/login/google
- Replace https://grafana.mycompany.com with the URL of your Grafana instance.
2020-10-01 11:45:05 -05:00
1. Click Create
1. Copy the Client ID and Client Secret from the 'OAuth Client' modal
2018-09-06 05:11:56 -05:00
## Enable Google OAuth in Grafana
2023-05-18 09:50:20 -05:00
Specify the Client ID and Secret in the [Grafana configuration file ]({{< relref "../../../configure-grafana#configuration-file-location" >}} ). For example:
2018-09-06 05:11:56 -05:00
```bash
[auth.google]
enabled = true
2023-01-19 08:53:02 -06:00
allow_sign_up = true
auto_login = false
2018-09-06 05:11:56 -05:00
client_id = CLIENT_ID
client_secret = CLIENT_SECRET
scopes = https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email
auth_url = https://accounts.google.com/o/oauth2/auth
token_url = https://accounts.google.com/o/oauth2/token
allowed_domains = mycompany.com mycompany.org
2023-01-05 13:04:04 -06:00
hosted_domain = mycompany.com
2023-05-30 11:17:45 -05:00
use_pkce = true
2018-09-06 05:11:56 -05:00
```
2020-11-09 14:26:49 -06:00
You may have to set the `root_url` option of `[server]` for the callback URL to be
2018-10-11 14:22:02 -05:00
correct. For example in case you are serving Grafana behind a proxy.
2018-09-06 05:11:56 -05:00
Restart the Grafana back-end. You should now see a Google login button
on the login page. You can now login or sign up with your Google
accounts. The `allowed_domains` option is optional, and domains were separated by space.
You may allow users to sign-up via Google authentication by setting the
`allow_sign_up` option to `true` . When this option is set to `true` , any
user successfully authenticating via Google authentication will be
automatically signed up.
2022-11-14 09:47:46 -06:00
2023-01-05 13:04:04 -06:00
You may specify a domain to be passed as `hd` query parameter accepted by Google's
OAuth 2.0 authentication API. Refer to Google's OAuth [documentation ](https://developers.google.com/identity/openid-connect/openid-connect#hd-param ).
2023-05-30 11:17:45 -05:00
### PKCE
IETF's [RFC 7636 ](https://datatracker.ietf.org/doc/html/rfc7636 )
introduces "proof key for code exchange" (PKCE) which provides
additional protection against some forms of authorization code
interception attacks. PKCE will be required in [OAuth 2.1 ](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-v2-1-03 ).
> You can disable PKCE in Grafana by setting `use_pkce` to `false` in the`[auth.google]` section.
2022-11-14 09:47:46 -06:00
### Configure refresh token
> Available in Grafana v9.3 and later versions.
> **Note:** This feature is behind the `accessTokenExpirationCheck` feature toggle.
When a user logs in using an OAuth provider, Grafana verifies that the access token has not expired. When an access token expires, Grafana uses the provided refresh token (if any exists) to obtain a new access token.
Grafana uses a refresh token to obtain a new access token without requiring the user to log in again. If a refresh token doesn't exist, Grafana logs the user out of the system after the access token has expired.
By default, Grafana includes the `access_type=offline` parameter in the authorization request to request a refresh token.
2023-01-19 02:54:22 -06:00
2023-01-19 08:53:02 -06:00
### Configure automatic login
Set `auto_login` option to true to attempt login automatically, skipping the login screen.
This setting is ignored if multiple auth providers are configured to use auto login.
```
auto_login = true
```
2023-01-19 02:54:22 -06:00
## Skip organization role sync
We do not currently sync roles from Google and instead set the AutoAssigned role to the user at first login. To manage your user's organization role from within Grafana, set `skip_org_role_sync` to `true` .
```ini
[auth.google]
# ..
skip_org_role_sync = true
```