From c99079b83a4f57df4e4c731921b9f3961690c35a Mon Sep 17 00:00:00 2001
From: Felipe Reyes <felipe.reyes@canonical.com>
Date: Wed, 17 Sep 2025 15:58:29 -0300
Subject: [PATCH] Enable global cache by default

The commit d2e42f1 introduced the config option enable-cache set to
False by default to cache inconsistency when keystone was deployed in
HA, since then a new change by made to disable token caching (563b453),
it has tested that this option alleviates the performance regression
seen when disabling the cache, whitout leaving the system exposed to
expired token reuse.

Change-Id: I584b7d2ea03d824c229cf5b21723d3645ffc2056
Related-Bug: #2113772
Related-Bug: #2089616
Signed-off-by: Felipe Reyes <felipe.reyes@canonical.com>
---
 config.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.yaml b/config.yaml
index bba86817..1427850f 100644
--- a/config.yaml
+++ b/config.yaml
@@ -136,7 +136,7 @@ options:
       cache expiration time.
   enable-cache:
     type: boolean
-    default: False
+    default: True
     description: |
       Enable caching across Keystone using unit localised memcache; enabling
       this feature may cause caching inconsistency in multi-unit deployments