SAML authentication

    The SAML single sign-on (SSO) standard is varied and flexible. Our implementation contains a subset of features needed to provide a smooth authentication experience into Grafana.

    Grafana supports the following SAML 2.0 bindings:

    • From the Service Provider (SP) to the Identity Provider (IdP):

      • binding

    • From the Identity Provider (IdP) to the Service Provider (SP):

      • HTTP-POST binding

    In terms of security:

    • Grafana supports signed and encrypted assertions.
    • Grafana does not support signed or encrypted requests.

    In terms of initiation:

    • Grafana supports SP-initiated requests.
    • Grafana does not support IdP-initiated request.

    The table below describes all SAML configuration options. Continue reading below for details on specific options. Like any other Grafana configuration, you can apply these options as environment variables.

    To use the SAML integration, in the auth.saml section of in the Grafana custom configuration file, set enabled to true.

    Refer to Configuration for more information about configuring Grafana.

    Certificate and private key

    The SAML SSO standard uses asymmetric encryption to exchange information between the SP (Grafana) and the IdP. To perform such encryption, you need a public part and a private part. In this case, the X.509 certificate provides the public part, while the private key provides the private part.

    Grafana supports two ways of specifying both the certificate and private_key.

    • Without a suffix (certificate or private_key), the configuration assumes you’ve supplied the base64-encoded file contents.
    • With the _path suffix (certificate_path or private_key_path), then Grafana treats the value entered as a file path and attempts to read the file from the file system.

    You can only use one form of each configuration option. Using multiple forms, such as both certificate and certificate_path, results in an error.

    Signature algorithm

    Only available in Grafana v7.3+

    The SAML standard recommends using a digital signature for some types of messages, like authentication or logout requests. If the signature_algorithm option is configured, Grafana will put a digital signature into SAML requests. Supported signature types are rsa-sha1, rsa-sha256, rsa-sha512. This option should match your IdP configuration, otherwise, signature validation will fail. Grafana uses key and certificate configured with private_key and certificate options for signing SAML requests.

    IdP metadata

    You also need to define the public part of the IdP for message verification. The SAML IdP metadata XML defines where and how Grafana exchanges user information.

    Grafana supports three ways of specifying the IdP metadata.

    • Without a suffix idp_metadata, Grafana assumes base64-encoded XML file contents.
    • With the _path suffix, Grafana assumes a file path and attempts to read the file from the file system.
    • With the _url suffix, Grafana assumes a URL and attempts to load the metadata from the given location.

    Maximum issue delay

    Prevents SAML response replay attacks and internal clock skews between the SP (Grafana) and the IdP. You can set a maximum amount of time between the IdP issuing a response and the SP (Grafana) processing it.

    The configuration options is specified as a duration, such as max_issue_delay = 90s or max_issue_delay = 1h.

    SP metadata is likely to expire at some point, perhaps due to a certificate rotation or change of location binding. Grafana allows you to specify for how long the metadata should be valid. Leveraging the validUntil field, you can tell consumers until when your metadata is going to be valid. The duration is computed by adding the duration to the current time.

    The configuration option is specified as a duration, such as metadata_valid_duration = 48h.

    Identity provider (IdP) registration

    For the SAML integration to work correctly, you need to make the IdP aware of the SP.

    • The /saml/metadata endpoint, which contains the SP metadata. You can either download and upload it manually, or youmake the IdP request it directly from the endpoint. Some providers name it Identifier or Entity ID.
    • The /saml/acs endpoint, which is intended to receive the ACS (Assertion Customer Service) callback. Some providers name it SSO URL or Reply URL.

    IdP-initiated Single Sign-On (SSO)

    By default, Grafana allows only service provider (SP) initiated logins (when the user logs in with SAML via Grafana’s login page). If you want users to log in into Grafana directly from your identity provider (IdP), set the allow_idp_initiated configuration option to and configure relay_state with the same value specified in the IdP configuration.

    IdP-initiated SSO has some security risks, so make sure you understand the risks before enabling this feature. When using IdP-initiated SSO, Grafana receives unsolicited SAML requests and can’t verify that login flow was started by the user. This makes it hard to detect whether SAML message has been stolen or replaced. Because of this, IdP-initiated SSO is vulnerable to login cross-site request forgery (CSRF) and man in the middle (MITM) attacks. We do not recommend using IdP-initiated SSO and keeping it disabled whenever possible.

    Single logout

    Only available in Grafana v7.3+

    SAML’s single logout feature allows users to log out from all applications associated with the current IdP session established via SAML SSO. If the single_logout option is set to true and a user logs out, Grafana requests IdP to end the user session which in turn triggers logout from all other applications the user is logged into using the same IdP session (applications should support single logout). Conversely, if another application connected to the same IdP logs out using single logout, Grafana receives a logout request from IdP and ends the user session.

    Assertion mapping

    During the SAML SSO authentication flow, Grafana receives the ACS callback. The callback contains all the relevant information of the user under authentication embedded in the SAML response. Grafana parses the response to create (or update) the user within its internal database.

    For Grafana to map the user information, it looks at the individual attributes within the assertion. You can think of these attributes as Key/Value pairs (although, they contain more information than that).

    Grafana provides configuration options that let you modify which keys to look at for these values. The data we need to create the user in Grafana is Name, Login handle, and email.

    To use SAML Team sync, set to the attribute name where you store user groups. Then Grafana will use attribute values extracted from SAML assertion to add user into the groups with the same name configured on the External group sync tab.

    Learn more about Team Sync

    Configure role sync

    Only available in Grafana v7.0+

    Role sync allows you to map user roles from an identity provider to Grafana. To enable role sync, configure role attribute and possible values for the Editor, and Grafana Admin roles.

    1. In the configuration file, set option to the attribute name where the role information will be extracted from.
    2. Set the role_values_editor option to the values mapped to the Editor role.
    3. Set the option to the values mapped to the organization Admin role.
    4. Set the role_values_grafana_admin option to the values mapped to the Grafana Admin role.

    If a user role doesn’t match any of configured values, then the Viewer role will be assigned.

    Refer to for more information about roles and permissions in Grafana.

    Example configuration:

    Important: When role sync is configured, any changes of user roles and organization membership made manually in Grafana will be overwritten on next user login. Assign user organizations and roles in the IdP instead.

    Configure organization mapping

    Organization mapping allows you to assign users to particular organization in Grafana depending on attribute value obtained from identity provider.

    1. In configuration file, set to the attribute name you store organization info in.
    2. Set org_mapping option to the comma-separated list of Organization:OrgId pairs to map organization from IdP to Grafana organization specified by id.

    For example, use following configuration to assign users from Engineering organization to the Grafana organization with id 2 and users from Sales - to the org with id 3, based on Org assertion attribute value:

    You can specify multiple organizations both for the IdP and Grafana:

    • org_mapping = Engineering:2, Sales:2 to map users from Engineering and Sales to 2 in Grafana.
    • org_mapping = Engineering:2, Engineering:3 to assign Engineering to both 2 and 3 in Grafana.

    Configure allowed organizations

    Only available in Grafana v7.0+

    This guide will follow you through the steps of configuring SAML authentication in Grafana with Okta. You need to be an admin in your Okta organization to access Admin Console and create SAML integration. You also need permissions to edit Grafana config file and restart Grafana server.

    Configure the SAML integration in Okta

    To configure SAML integration with Okta, create integration inside the Okta organization first.

    1. Log in to the Okta portal.

    2. Go to the Admin Console in your Okta organization by clicking Admin in the upper-right corner. If you are in the Developer Console, then click Developer Console in the upper-left corner and then click Classic UI to switch over to the Admin Console.

    3. Click Add Application.

    4. Click Create New App to start the Application Integration Wizard.

    5. Choose Web as a platform.

    6. Select SAML 2.0 in the Sign on method section.

    7. Click Create.

    8. On the General Settings tab, enter a name for your Grafana integration. You can also upload a logo.

    9. On the Configure SAML tab, enter the SAML information related to your Grafana instance:

      • In the Single sign on URL field, use the /saml/acs endpoint URL of your Grafana instance, for example, https://grafana.example.com/saml/acs.

      • In the Audience URI (SP Entity ID) field, use the /saml/metadata endpoint URL, for example, https://grafana.example.com/saml/metadata.

      • Leave the default values for Name ID format and Application username.

      • In the ATTRIBUTE STATEMENTS (OPTIONAL) section, enter the SAML attributes to be shared with Grafana, for example:

        Attribute name (in Grafana)Value (in Okta profile)
        Loginuser.login
        Emailuser.email
        DisplayNameuser.firstName + “ “ + user.lastName

      • In the GROUP ATTRIBUTE STATEMENTS (OPTIONAL) section, enter a group attribute name (for example, Group) and set filter to Matches regex .* to return all user groups.

    10. Click Next.

    11. On the final Feedback tab, fill out the form and then click Finish.

    Once the application is created, configure Grafana to use it for SAML authentication. Refer to Configuration to get more information about how to configure Grafana.

    1. In the [auth.saml] section in the Grafana configuration file, set to .
    2. Configure the certificate and private key.
    3. On the Okta application page where you have been redirected after application created, navigate to the Sign On tab and find Identity Provider metadata link in the Settings section.
    4. Set the to the URL obtained from the previous step. The URL should look like https://<your-org-id>.okta.com/app/<application-id>/sso/saml/metadata.
    5. Set the following options to the attribute names configured at the step 10 of the SAML integration setup. You can find this attributes on the General tab of the application page (ATTRIBUTE STATEMENTS and GROUP ATTRIBUTE STATEMENTS in the SAML Settings section).

    When you are finished, the Grafana configuration might look like this example:

    To troubleshoot and get more log information, enable SAML debug logging in the configuration file. Refer to for more information.