From 3dbda43d4481d1cbf78e6035369444d2ef87f34b Mon Sep 17 00:00:00 2001 From: Misi Date: Fri, 13 Oct 2023 17:27:16 +0200 Subject: [PATCH] Docs: Update whats-new-next with RBAC permission validation (#76470) * Update whats-new-next with RBAC permission validation * run prettier * Fixed version syntax * Update docs/sources/whatsnew/whats-new-next/index.md Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com> * update docs * update * fix merge --------- Co-authored-by: Isabel <76437239+imatwawana@users.noreply.github.com> --- docs/sources/whatsnew/whats-new-next/index.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/sources/whatsnew/whats-new-next/index.md b/docs/sources/whatsnew/whats-new-next/index.md index d793ac7c450..5260f93c21d 100644 --- a/docs/sources/whatsnew/whats-new-next/index.md +++ b/docs/sources/whatsnew/whats-new-next/index.md @@ -159,3 +159,16 @@ _Available in private preview in Grafana Cloud_ The Grafana Assume Role authentication provider lets Grafana Cloud users of the CloudWatch data source authenticate with AWS without having to create and maintain long term AWS Users. Using the new assume role authentication method, you no longer have to rotate access and secret keys in your CloudWatch data source. Instead, Grafana Cloud users can create an identity access and management (IAM) role that has a trust relationship with Grafana's AWS account; Grafana's AWS account will then use AWS Secure Token Service (STS) to create temporary credentials to access the user's AWS data. To learn more, refer to the [CloudWatch authentication documentation](/docs/grafana/next/datasources/aws-cloudwatch/aws-authentication). + +## Permission validation on custom role creation and update + + + + + + +August 25, 2023 + +_Generally available in Grafana Cloud_ + +With the current release, we enabled RBAC permission validation (`rbac.permission_validation_enabled` setting) by default. This means that the permissions provided in the request during custom role creation or update are validated against the list of [available permissions and their scopes](https://grafana.com/docs/grafana//administration/roles-and-permissions/access-control/custom-role-actions-scopes/#action-definitions). If the request contains a permission that is not available or the scope of the permission is not valid, the request is rejected with an error message.