From 6da051b1f229235ef5956df18c2894198ce3a807 Mon Sep 17 00:00:00 2001 From: Huabing Zhao Date: Fri, 20 Sep 2024 20:46:14 +0800 Subject: [PATCH] chore: fix the incorrect `scope` claim name in the API doc (#36241) Signed-off-by: Huabing Zhao --- api/envoy/extensions/filters/http/jwt_authn/v3/config.proto | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/api/envoy/extensions/filters/http/jwt_authn/v3/config.proto b/api/envoy/extensions/filters/http/jwt_authn/v3/config.proto index 85f96eeef873..99212f3edfd9 100644 --- a/api/envoy/extensions/filters/http/jwt_authn/v3/config.proto +++ b/api/envoy/extensions/filters/http/jwt_authn/v3/config.proto @@ -63,9 +63,9 @@ message JwtProvider { message NormalizePayload { // Each claim in this list will be interpreted as a space-delimited string // and converted to a list of strings based on the delimited values. - // Example: a token with a claim ``scopes: "email profile"`` is translated - // to dynamic metadata ``scopes: ["email", "profile"]`` if this field is - // set value ``["scopes"]``. This special handling of ``scopes`` is + // Example: a token with a claim ``scope: "email profile"`` is translated + // to dynamic metadata ``scope: ["email", "profile"]`` if this field is + // set value ``["scope"]``. This special handling of ``scope`` is // recommended by `RFC8693 // `_. repeated string space_delimited_claims = 1;