In a scenario where an environment has a unreliable keycloak database and/or instance, users increase the broker authentication cache to reduce impact. However, if a client authenticates to the broker and keycloak is unavailable, the authentication failure is cached and the broker will not attempt to try keycloak again, even after keycloak has become available.

This request is similar to the ldap configuration to avoid caching certain errors/exceptions as authentication failures.