From 65eb601578dfb386cee21c0d4d103a5862625572 Mon Sep 17 00:00:00 2001 From: Matthias Hanel Date: Wed, 10 Feb 2021 15:49:17 -0500 Subject: [PATCH] Update nats-server/configuration/securing_nats/jwt/resolver.md Co-authored-by: Colin Sullivan --- nats-server/configuration/securing_nats/jwt/resolver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nats-server/configuration/securing_nats/jwt/resolver.md b/nats-server/configuration/securing_nats/jwt/resolver.md index 15eb685..054b9fe 100644 --- a/nats-server/configuration/securing_nats/jwt/resolver.md +++ b/nats-server/configuration/securing_nats/jwt/resolver.md @@ -73,7 +73,7 @@ There, they may be subject to updates. Restarts of the `nats-server` will hold o Not every server in a cluster needs to be set to `full`. You need enough to still serve your workload adequately, while some server are offline. -### cache +### Cache This resolver only stores a subset of [JWT](../../nats-server/configuration/securing_nats/jwt/) and evicts extra ones based on an LRU scheme. Missing jwt are downloaded from `full` nats based resolver.