From 8c7d2e8922bff3189ea4933fcdde442f772c345d Mon Sep 17 00:00:00 2001 From: Hao Date: Tue, 11 Mar 2025 15:01:17 +0800 Subject: [PATCH] Fix typo in multitenancy documentation Signed-off-by: Hao --- .../ROOT/pages/servlet/oauth2/resource-server/multitenancy.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/servlet/oauth2/resource-server/multitenancy.adoc b/docs/modules/ROOT/pages/servlet/oauth2/resource-server/multitenancy.adoc index 3982f855cc..938ca0154b 100644 --- a/docs/modules/ROOT/pages/servlet/oauth2/resource-server/multitenancy.adoc +++ b/docs/modules/ROOT/pages/servlet/oauth2/resource-server/multitenancy.adoc @@ -320,7 +320,7 @@ class TenantJWSKeySelector(tenants: TenantRepository) : JWTClaimsSetAwareJWSKeyS ---- ====== <1> A hypothetical source for tenant information -<2> A cache for `JWKKeySelector`s, keyed by tenant identifier +<2> A cache for `JWSKeySelector`s, keyed by tenant identifier <3> Looking up the tenant is more secure than simply calculating the JWK Set endpoint on the fly - the lookup acts as a list of allowed tenants <4> Create a `JWSKeySelector` via the types of keys that come back from the JWK Set endpoint - the lazy lookup here means that you don't need to configure all tenants at startup