From 547883015023a887250388c8e492d8202ae76e8f Mon Sep 17 00:00:00 2001 From: Ronald Ekambi Date: Tue, 20 Jun 2023 16:33:24 +0000 Subject: [PATCH 1/2] backport of commit 452d08d5e8e40c0710a2042dd1d67b8eaa5fe43d --- .../connect/config-entries/jwt-provider.mdx | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/website/content/docs/connect/config-entries/jwt-provider.mdx b/website/content/docs/connect/config-entries/jwt-provider.mdx index b31427af4ff..ba7d4a28bf9 100644 --- a/website/content/docs/connect/config-entries/jwt-provider.mdx +++ b/website/content/docs/connect/config-entries/jwt-provider.mdx @@ -952,6 +952,22 @@ Defines behavior for caching the validation result of previously encountered JWT +## Metrics + +The following `envoy` metrics can be used to track jwt authentication details. + +~> **Note:** Envoy does not currently provide any documentation on these metrics. + +```yaml +http.ingress_http.jwt_authn.allowed +http.ingress_http.jwt_authn.cors_preflight_bypassed +http.ingress_http.jwt_authn.denied +http.ingress_http.jwt_authn.jwks_fetch_failed +http.ingress_http.jwt_authn.jwks_fetch_success +http.ingress_http.jwt_authn.jwt_cache_hit +http.ingress_http.jwt_authn.jwt_cache_miss +``` + ## Examples The following examples demonstrate common JWT provider configuration patterns for specific use cases. @@ -1023,4 +1039,4 @@ spec: ``` - \ No newline at end of file + From 5056a18626530edde941abfe8c39f447d025ffef Mon Sep 17 00:00:00 2001 From: Ronald Ekambi Date: Tue, 20 Jun 2023 18:29:39 +0000 Subject: [PATCH 2/2] backport of commit 1f1f222c97f981a23de44be2afdef37c25f4a91a --- .../docs/connect/config-entries/jwt-provider.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/website/content/docs/connect/config-entries/jwt-provider.mdx b/website/content/docs/connect/config-entries/jwt-provider.mdx index ba7d4a28bf9..f003106a330 100644 --- a/website/content/docs/connect/config-entries/jwt-provider.mdx +++ b/website/content/docs/connect/config-entries/jwt-provider.mdx @@ -959,13 +959,13 @@ The following `envoy` metrics can be used to track jwt authentication details. ~> **Note:** Envoy does not currently provide any documentation on these metrics. ```yaml -http.ingress_http.jwt_authn.allowed -http.ingress_http.jwt_authn.cors_preflight_bypassed -http.ingress_http.jwt_authn.denied -http.ingress_http.jwt_authn.jwks_fetch_failed -http.ingress_http.jwt_authn.jwks_fetch_success -http.ingress_http.jwt_authn.jwt_cache_hit -http.ingress_http.jwt_authn.jwt_cache_miss +http.public_listener.jwt_authn.allowed +http.public_listener.jwt_authn.cors_preflight_bypassed +http.public_listener.jwt_authn.denied +http.public_listener.jwt_authn.jwks_fetch_failed +http.public_listener.jwt_authn.jwks_fetch_success +http.public_listener.jwt_authn.jwt_cache_hit +http.public_listener.jwt_authn.jwt_cache_miss ``` ## Examples