--- title: "Cache persistence" slug: "oas-pg-cache-persistence-3-29" updated: 2026-01-12T10:22:51Z published: 2026-01-14T17:25:16Z canonical: "docs.onespan.com/oas-pg-cache-persistence-3-29" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Cache persistence Certain multi-step workflows in OneSpan Authentication Server require caching, because state information that is shared between individual steps must be available within OneSpan Authentication Server. These workflows include: - Authentication using push notifications - Authentication using Challenge/Response (with or without Secure Channel) - Provisioning (Standard and multi-device licensing) - Signature validation with Secure Channel - Administrative sessions When multiple OneSpan Authentication Server instances are working together, the multi-step commands use a cache written to the database, which is available to all OneSpan Authentication Server instances that share the same database. This allows multi-step commands to be sent to any OneSpan Authentication Server instance that is part of the setup, i.e. share the same database. This persistent cache mechanism removes in-memory cache limits. Moreover, the OneSpan Authentication Server service/daemon can be restarted without losing sessions. The Administration Web Interface supports cache-specific settings. These cache settings can be found in SERVERS > Global Configuration. > Cache persistence is an important element used for the high-availability and maximum-availability deployment models. > > In the advanced deployment model caches are persistent for each OneSpan Authentication Server instance. However, cache data is not replicated between the instances using the OneSpan Authentication Server replication mechanism. > > For more information about the different deployment models, refer to the OneSpan Authentication Server Performance and Deployment Guide.