Auth caching policy is not behaving as expected when backend-listener returns a 5XX status code

Solution Verified - Updated -

Issue

  • The auth caching policy is configured with resilient mode but when backend-listener returns a 5XX status code the API requests still fail.
  • How to configure the auth caching policy to allow previously authorised requests through when backend-listener returns a 5XX status code?

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content