From 2182f4829e92146de458cb2752e32923b3a5e716 Mon Sep 17 00:00:00 2001 From: Vardan Torosyan Date: Thu, 12 Dec 2024 15:17:23 +0100 Subject: [PATCH] Docs: Refer to the org header usage in JWT docs (#96549) --- .../configure-security/configure-authentication/jwt/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/sources/setup-grafana/configure-security/configure-authentication/jwt/index.md b/docs/sources/setup-grafana/configure-security/configure-authentication/jwt/index.md index beffabd14f7..dc73b488a1b 100644 --- a/docs/sources/setup-grafana/configure-security/configure-authentication/jwt/index.md +++ b/docs/sources/setup-grafana/configure-security/configure-authentication/jwt/index.md @@ -199,7 +199,8 @@ expect_claims = {"iss": "https://your-token-issuer", "your-custom-claim": "foo"} Grafana checks for the presence of a role using the [JMESPath](http://jmespath.org/examples.html) specified via the `role_attribute_path` configuration option. The JMESPath is applied to JWT token claims. The result after evaluation of the `role_attribute_path` JMESPath expression should be a valid Grafana role, for example, `None`, `Viewer`, `Editor` or `Admin`. -The organization that the role is assigned to can be configured using the `X-Grafana-Org-Id` header. +To assign the role to a specific organization include the `X-Grafana-Org-Id` header along with your JWT when making API requests to Grafana. +To learn more about the header, please refer to the [documentation]({{< relref "../../../../developers/http_api#x-grafana-org-id-header" >}}). ### JMESPath examples