anchor.diff:  |azure|TCP|AZURE_PING
   |===
   
  -For the cloud vendor specific stacks to work, you have to provide additional dependencies to Keycloak. You can find more information, including Links to repositories providing the additional dependencies, in the https://infinispan.org/docs/dev/titles/embedding/embedding.html#jgroups-cloud-discovery-protocols_cluster-transport[official Infinispan documentation].
  +Cloud vendor specific stacks have additional dependencies for Keycloak.
  +For more information and links to repositories with these dependencies, see the https://infinispan.org/docs/dev/titles/embedding/embedding.html#jgroups-cloud-discovery-protocols_cluster-transport[Infinispan documentation].
   
  -To provide the dependencies to Keycloak, put the respective JAR in the `providers` directory and `build` Keycloak afterwards, using
  +To provide the dependencies to Keycloak, put the respective JAR in the `providers` directory and `build` Keycloak by entering this command:
   
   <@kc.build parameters="--cache-stack=<ec2|google|azure>"/>
   
   === Securing cache communication
  -The current Infinispan cache implementation should be secured by various security measures such as RBAC, ACLs and Transport stack encryption. Please refer to the https://infinispan.org/docs/dev/titles/security/security.html#[Infinispan security guide] for more information about securing cache communication.
  +The current Infinispan cache implementation should be secured by various security measures such as RBAC, ACLs, and Transport stack encryption. For more information about securing cache communication, see the https://infinispan.org/docs/dev/titles/security/security.html#[Infinispan security guide].
   
   </@tmpl.guide>
  
positive.code: |actionTokens|Distributed|Caches action Tokens
  |====
  
  Local caches for realms, users and authorization are configured to have 10000 entries per default. The local key cache can hold up to 1000 entries per default and defaults to expire every 1h, so keys are forced to be periodically downloaded from external clients or identity providers.
  
  All distributed caches are set to have 2 owners per default, meaning 2 nodes having a copy of the specific cache entries. Non-owner nodes query the owners of a specific cache to obtain data. When both owner nodes are offline, all data gets lost. This usually leads to users being logged out at the next request and having to login again.
  
  === Specify your own cache configuration file
  
  To specify your own cache configuration file, use:
  
  <@kc.build parameters="--cache-config-file=my-cache-file.xml"/>
  
  == Transport stacks
  Transport stacks ensure that distributed cache nodes in a cluster communicate in a reliable fashion. Keycloak supports a wide range of transport stacks:
  
  <@opts.expectedValues option="cache-stack"/>
  
  To apply a specific cache stack, use:
  
  <@kc.build parameters="--cache-stack=<stack>"/>
  
  
negative.code: summary="Understand how to configure the caching layer"
  includedOptions="cache cache-*">
  
  Keycloak is designed for high availability and multi-node clustered setups.
  The current distributed cache implementation is built on top of https://infinispan.org[Infinispan], a high-performance, distributable in-memory data grid.
  
  All available cache options are build options, so they need to be applied to a `build` of Keycloak before starting.
  
  == Enable distributed caching
  When you start Keycloak in production mode, by using the `start` command, caching is enabled and all Keycloak nodes in your network are discovered.
  
  To explicitly enable distributed infinispan caching, enter this command:
  
  <@kc.build parameters="--cache=ispn"/>
  
  When you start Keycloak in development mode, by using the `start-dev` command, Keycloak uses only local caches, applying the `--cache=local` option.
  The `local` cache mode is intended only for development and testing purposes.
  
  == Configuring caches
  Keycloak provides a cache configuration file with sensible defaults located at `conf/cache-ispn.xml`.
  
  The cache configuration is a regular https://infinispan.org/docs/stable/titles/configuring/configuring.html[Infinispan configuration file].
  
  === Cache types and defaults
  
  .Local caches
  Keycloak caches persistent data locally to avoid unnecessary database requests.
  The following caches are used:
  
  * realms
  * users
  