Skip to main content
Caches store connector tokens and provider data (OIDC authorization codes, SAML request data, and other frequently accessed information). Caches are configured under the caches[] top-level key and are independent of session storage — they serve different purposes.
Production support status:
  • Redis cache — Supported for production. Use Redis caches for OIDC Provider, SAML Provider, and Service Extension data in multi-node deployments.
  • Cluster cache — Experimental. Requires the experimental.clusters feature flag. Not recommended for production workloads. This feature may be changed or removed without notice.
Console terminology: In the Maverics Console, Orchestrator instances and configuration delivery are managed through Deployments. When working directly with YAML, configuration is managed as files delivered via the -config flag or MAVERICS_CONFIG environment variable.

Overview

Caches are named and referenced by connectors and providers (e.g., oidcProvider.cache: my-redis). They are configured independently of session stores and serve a different role: caches store connector tokens, OIDC/SAML provider data, and other frequently accessed information, while session stores persist user authentication state.
The local_default cache is always automatically registered. You do not need to configure it. The name local_default is reserved and cannot be used for custom caches.

Cache Types

TypeDescriptionUse Case
redisRedis-backed cacheMulti-node deployments, shared token cache across Orchestrator instances
clusterOrchestrator cluster-backed cacheDistributed cache via Orchestrator clustering (requires cluster configuration)

Cache Detail Pages

Configuration Reference

Cache Type Values

Type ValueDescription
redisRedis-backed distributed cache
clusterOrchestrator cluster-backed cache

Cluster Cache Fields

KeyTypeDefaultRequiredDescription
caches[].namestringYesUnique cache name
caches[].typestringYesCache type: "cluster"
caches[].cluster.namestringYesReference to a defined cluster name

Cache Options

The following options apply to both Redis and cluster cache types:
KeyTypeDefaultDescription
caches[].keys.disablePrefixbooleanfalseDisable feature-specific key prefix (useful for Service Extensions reading non-Orchestrator data)
caches[].encryption.disabledbooleanfalseDisable cache value encryption (encryption is enabled by default)
caches[].encryption.keys.currentstringAES-256 encryption key (64 hex characters / 32 bytes)
caches[].encryption.keys.oldarray[]Previous encryption keys for key rotation
caches[].hashing.keys.disabledbooleanfalseDisable cache key hashing (hashing is enabled by default)
The local_default cache name is reserved and cannot be used for custom cache definitions. A default unbounded local cache is always registered automatically.

Cross-Reference

Configuration details for Redis cache fields are on the Redis Cache page.