Files
2023-12-14 14:14:03 -05:00

40 lines
1.4 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
description: Upgrade to Grafana v10.1
keywords:
- grafana
- configuration
- documentation
- upgrade
title: Upgrade to Grafana v10.1
menuTitle: Upgrade to v10.1
weight: 1600
---
# Upgrade to Grafana v10.1
{{< docs/shared lookup="upgrade/intro.md" source="grafana" version="<GRAFANA VERSION>" >}}
{{< docs/shared lookup="back-up/back-up-grafana.md" source="grafana" version="<GRAFANA VERSION>" leveloffset="+1" >}}
{{< docs/shared lookup="upgrade/upgrade-common-tasks.md" source="grafana" version="<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 users 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:
```ini
[auth.generic_oauth]
...
skip_org_role_sync = true
```