This is documentation for the next version of Grafana. For the latest stable release, go to the latest version.

Documentation Grafana documentation Set up Configure security Configure authentication Okta OIDC

Configure Okta OIDC authentication

There are numerous authentication methods available in Grafana to verify user identity. The authentication configuration dictates which users can access Grafana and the methods they can use for logging in. You can also configure Grafana to automatically update users’ roles and team memberships in Grafana based on the information returned by the auth provider integration.

When deciding on an authentication method, it’s important to take into account your current identity and access management system as well as the specific authentication and authorization features you require. For a complete list of the available authentication options and the features they support, refer to Configure authentication.

Before you begin

To follow this guide, ensure you have permissions in your Okta workspace to create an OIDC app.

Create an Okta app

1. From the Okta Admin Console, select Create App Integration from the Applications menu.

2. For Sign-in method, select OIDC - OpenID Connect.

3. For Application type, select Web Application and click Next.

4. Configure New Web App Integration Operations:

   • App integration name: Choose a name for the app.
   • Logo (optional): Add a logo.
   • Grant type: Select Authorization Code and Refresh Token.
   • Sign-in redirect URIs: Replace the default setting with the Grafana Cloud Okta path, replacing <YOUR_ORG> with the name of your Grafana organization: https://<YOUR_ORG>.grafana.net/login/okta. For on-premises installation, use the Grafana server URL: http://<my_grafana_server_name_or_ip>:<grafana_server_port>/login/okta.
   • Sign-out redirect URIs (optional): Replace the default setting with the Grafana Cloud Okta path, replacing <YOUR_ORG> with the name of your Grafana organization: https://<YOUR_ORG>.grafana.net/logout. For on-premises installation, use the Grafana server URL: http://<my_grafana_server_name_or_ip>:<grafana_server_port>/logout.
   • Base URIs (optional): Add any base URIs
   • Controlled access: Select whether to assign the app integration to everyone in your organization, or only selected groups. You can assign this option after you create the app.

5. Make a note of the following:

   • ClientID
   • Client Secret
   • Auth URL For example: https://<TENANT_ID>.okta.com/oauth2/v1/authorize
   • Token URL For example: https://<TENANT_ID>.okta.com/oauth2/v1/token
   • API URL For example: https://<TENANT_ID>.okta.com/oauth2/v1/userinfo

Configure Okta to Grafana role mapping

1. In the Okta Admin Console, select Directory > Profile Editor.

2. Select the Okta Application Profile you created previously (the default name for this is <App name> User).

3. Select Add Attribute and fill in the following fields:

   • Data Type: string
   • Display Name: Meaningful name. For example, Grafana Role.
   • Variable Name: Meaningful name. For example, grafana_role.
   • Description (optional): A description of the role.
   • Enum: Select Define enumerated list of values and add the following:
     • Display Name: Admin Value: Admin
     • Display Name: Editor Value: Editor
     • Display Name: Viewer Value: Viewer

   The remaining attributes are optional and can be set as needed.

4. Click Save.

5. (Optional) You can add the role attribute to the default User profile. To do this, please follow the steps in the Optional: Add the role attribute to the User (default) Okta profile section.

Configure Groups claim

1. In the Okta Admin Console, select Application > Applications.
2. Select the OpenID Connect application you created.
3. Go to the Sign On tab and click Edit in the OpenID Connect ID Token section.
4. In the Group claim type section, select Filter.
5. In the Group claim filter section, leave the default name groups (or add it if the box is empty), then select Matches regex and add the following regex: .*.
6. Click Save.
7. Click the Back to applications link at the top of the page.
8. From the More button dropdown menu, click Refresh Application Data.
9. Include the groups scope in the Scopes field in Grafana of the Okta integration. For Terraform or in the Grafana configuration file, include the groups scope in scopes field.

Optional: Add the role attribute to the User (default) Okta profile

If you want to configure the role for all users in the Okta directory, you can add the role attribute to the User (default) Okta profile.

1. Return to the Directory section and select Profile Editor.
2. Select the User (default) Okta profile, and click Add Attribute.
3. Set all of the attributes in the same way you did in Step 3.
4. Select Add Mapping to add your new attributes. For example, user.grafana_role -> grafana_role.
5. To add a role to a user, select the user from the Directory, and click Profile -> Edit.
6. Select an option from your new attribute and click Save.
7. Update the Okta integration by setting the Role attribute path (role_attribute_path in Terraform and config file) to <YOUR_ROLE_VARIABLE>. For example: role_attribute_path = grafana_role (using the configuration).

Configure Okta authentication client using the Grafana UI

As a Grafana Admin, you can configure Okta OAuth2 client from within Grafana using the Okta UI. To do this, navigate to Administration > Authentication > Okta page and fill in the form. If you have a current configuration in the Grafana configuration file then the form will be pre-populated with those values otherwise the form will contain default values.

After you have filled in the form, click Save. If the save was successful, Grafana will apply the new configurations.

If you need to reset changes you made in the UI back to the default values, click Reset. After you have reset the changes, Grafana will apply the configuration from the Grafana configuration file (if there is any configuration) or the default values.

Refer to configuration options for more information.

Configure Okta authentication client using the Terraform provider

terraform Copy

resource "grafana_sso_settings" "okta_sso_settings" {
  provider_name = "okta"
  oauth2_settings {
    name                  = "Okta"
    auth_url              = "https://<okta tenant id>.okta.com/oauth2/v1/authorize"
    token_url             = "https://<okta tenant id>.okta.com/oauth2/v1/token"
    api_url               = "https://<okta tenant id>.okta.com/oauth2/v1/userinfo"
    client_id             = "CLIENT_ID"
    client_secret         = "CLIENT_SECRET"
    allow_sign_up         = true
    auto_login            = false
    scopes                = "openid profile email offline_access"
    role_attribute_path   = "contains(groups[*], 'Example::DevOps') && 'Admin' || 'None'"
    role_attribute_strict = true
    allowed_groups        = "Example::DevOps,Example::Dev,Example::QA"
  }
}

Go to Terraform Registry for a complete reference on using the grafana_sso_settings resource.

Configure Okta authentication client using the Grafana configuration file

Ensure that you have access to the Grafana configuration file.

Steps

To integrate your Okta OIDC provider with Grafana using our Okta OIDC integration, follow these steps:

1. Follow the Create an Okta app steps to create an OIDC app in Okta.

2. Refer to the following table to update field values located in the [auth.okta] section of the Grafana configuration file:

   Field	Description
   client_id	These values must match the client ID from your Okta OIDC app.
   auth_url	The authorization endpoint of your OIDC provider. https://<okta-tenant-id>.okta.com/oauth2/v1/authorize
   token_url	The token endpoint of your Okta OIDC provider. https://<okta-tenant-id>.okta.com/oauth2/v1/token
   api_url	The user information endpoint of your Okta OIDC provider. https://<tenant-id>.okta.com/oauth2/v1/userinfo
   enabled	Enables Okta OIDC authentication. Set this value to true.

3. Review the list of other Okta OIDC configuration options and complete them as necessary.

4. Optional: Configure a refresh token.

5. Configure role mapping.

6. Optional: Configure group synchronization.

7. Restart Grafana.

   You should now see a Okta OIDC login button on the login page and be able to log in or sign up with your OIDC provider.

The following is an example of a minimally functioning integration when configured with the instructions above:

ini Copy

[auth.okta]
name = Okta
icon = okta
enabled = true
allow_sign_up = true
client_id = <client id>
scopes = openid profile email offline_access
auth_url = https://<okta tenant id>.okta.com/oauth2/v1/authorize
token_url = https://<okta tenant id>.okta.com/oauth2/v1/token
api_url = https://<okta tenant id>.okta.com/oauth2/v1/userinfo
role_attribute_path = grafana_role
role_attribute_strict = true
allowed_groups = "Example::DevOps" "Example::Dev" "Example::QA"

Configure a refresh token

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 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.

To enable the Refresh Token head over the Okta application settings and:

1. Under General tab, find the General Settings section.
2. Within the Grant Type options, enable the Refresh Token checkbox.

At the configuration file, extend the scopes in [auth.okta] section with offline_access and set use_refresh_token to true.

Configure role mapping

The user’s role is retrieved using a JMESPath expression from the role_attribute_path configuration option against the api_url (/userinfo OIDC endpoint) endpoint payload.

If no valid role is found, the user is assigned the role specified by the auto_assign_org_role option. You can disable this default role assignment by setting role_attribute_strict = true. This setting denies user access if no role or an invalid role is returned after evaluating the role_attribute_path and the org_mapping expressions.

You can use the org_attribute_path and org_mapping configuration options to assign the user to organizations and specify their role. For more information, refer to Org roles mapping example. If both org role mapping (org_mapping) and the regular role mapping (role_attribute_path) are specified, then the user will get the highest of the two mapped roles.

To allow mapping Grafana server administrator role, use the allow_assign_grafana_admin configuration option. Refer to configuration options for more information.

In Create an Okta app, you created a custom attribute in Okta to store the role. You can use this attribute to map the role to a Grafana role by setting the role_attribute_path configuration option to the custom attribute name: role_attribute_path = grafana_role.

If you want to map the role based on the user’s group, you can use the groups attribute from the user info endpoint. An example of this is role_attribute_path = contains(groups[*], 'Example::DevOps') && 'Admin' || 'None'. You can find more examples of JMESPath expressions on the Generic OAuth page for JMESPath examples.

To learn about adding custom claims to the user info in Okta, refer to add custom claims.

Org roles mapping example

In this example, the org_mapping uses the groups attribute as the source (org_attribute_path) to map the current user to different organizations and roles. The user has been granted the role of a Viewer in the org_foo org if they are a member of the Group 1 group, the role of an Editor in the org_bar org if they are a member of the Group 2 group, and the role of an Editor in the org_baz(OrgID=3) org.

Config:

ini Copy

org_attribute_path = groups
org_mapping = ["Group 1:org_foo:Viewer", "Group 2:org_bar:Editor", "*:3:Editor"]

Configure group synchronization (Enterprise only)

By using group synchronization, you can link your Okta groups to teams and roles within Grafana. This allows automatically assigning users to the appropriate teams or granting them the mapped roles. Teams and roles get synchronized when the user logs in.

Okta groups can be referenced by group names, like Admins or Editors.

To learn more about how to configure group synchronization, refer to Configure team sync and Configure group attribute sync documentation.

Configuration options

The following table outlines the various Okta OIDC configuration options. You can apply these options as environment variables, similar to any other configuration within Grafana. For more information, refer to Override configuration with environment variables.