Skip to main content
Version: 2.14 (latest)

resolver

Aliases: account_resolver, account_resolvers
Hot Reloadable
Resolver settings are rebuilt and swapped in on reload, but moving to or from an account resolver — enabling or disabling it — fails the reload.

Takes precedence over the value obtained from the operator if defined.

If a string value is used, it must be MEMORY or URL(<url>) where where url is an HTTP endpoint pointing to the NATS account resolver.

Note: the NATS account resolver is deprecated and the built-in NATS-based resolver should be used.

Types

TypeDescriptionChoices
string-
objectAn object with a set of explicit properties that can be set.-

Properties

NameDescriptionTypeDefaultReloadable
typeDefines whether the resolver type. A full resolver stores all account JWTs unless they are explicitly deleted. A cache resolver stores only a subset based on a least-recently-used (LRU) TTL.string-Yes*
dirThe path to storing account JWT files when pushed to the server.string-Yes*
limitIf set, limit the number of stored JWTs. In full mode, new JWTs will be rejected where as in cache mode, old JWTs will be evicted for new JWTs.integer-Yes*
ttlIf cache mode, defines how long an account JWT will be cached for before being considered for auto-eviction.duration-Yes*
intervalDefines the interval the resolver will randomly contact another server to reconcile JWTs, such as receiving new ones and deleting old ones. Applies to full mode only.duration-Yes*
timeoutDefines the request timeout for resolvers interacting with with other resolvers.duration-Yes*
allow_deleteIf true, allows JWTs to be deleted. Note, in full mode, this will result in the JWT file being renamed to with a .delete suffix, unless hard_delete is true.booleanfalseYes*
hard_deleteIf true, and the resolver is in full mode, deleted account JWTs will be removed from disk rather than having the .delete suffix appended.booleanfalseYes*

* See the property page for reload caveats.