Tested Versions

Before You Begin

You are required to utilize a unique client id and a unique and random client secret for all OpenID Connect relying parties. You should not use the client secret in this example, you should randomly generate one yourself. You may also choose to utilize a different client id, it’s completely up to you.

This example makes the following assumptions:

  • Application Root URL:
  • Authelia Root URL:
  • Client ID: grafana
  • Client Secret: grafana_client_secret



To configure Grafana to utilize Authelia as an OpenID Connect Provider:

  1. Add the following Generic OAuth configuration to the Grafana configuration:
enabled = true
name = Authelia
icon = signin
client_id = grafana
client_secret = grafana_client_secret
scopes = openid profile email groups
empty_scopes = false
auth_url =
token_url =
api_url =
login_attribute_path = preferred_username
groups_attribute_path = groups
name_attribute_path = name
use_pkce = true


The following YAML configuration is an example Authelia client configuration for use with Grafana which will operate with the above example:

- id: grafana
  secret: grafana_client_secret
  public: false
  authorization_policy: two_factor
    - openid
    - profile
    - groups
    - email
  userinfo_signing_algorithm: none

See Also