The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
grafana/docs/sources/upgrade-guide/upgrade-v10.1/index.md

1.4 KiB

description keywords title menuTitle weight
Upgrade to Grafana v10.1 [grafana configuration documentation upgrade] Upgrade to Grafana v10.1 Upgrade to v10.1 1600

Upgrade to Grafana v10.1

{{< docs/shared lookup="upgrade/intro.md" source="grafana" version="" >}}

{{< docs/shared lookup="back-up/back-up-grafana.md" source="grafana" version="" leveloffset="+1" >}}

{{< docs/shared lookup="upgrade/upgrade-common-tasks.md" source="grafana" version="" >}}

Technical notes

OAuth role mapping enforcement

This change impacts GitHub OAuth, Gitlab OAuth, Okta OAuth, and Generic OAuth.

Previously, if no organization role mapping was found for a user when they connected using OAuth, Grafana didn't update the user’s organization role.

With Grafana 10.1, on every login, if the role_attribute_path property doesn't return a role, then the user is assigned the role specified by the auto_assign_org_role option or the default role for the organization, which is Viewer by default.

To avoid overriding manually set roles, enable the skip_org_role_sync option in the Grafana configuration for your OAuth provider before upgrading to Grafana 10.1 and before users log in for the first time on Grafana 10.1.

Example for Generic OAuth2:

[auth.generic_oauth]
...
skip_org_role_sync = true