Batcher and Auth Caching Policies interfere with each other

Solution Verified - Updated -

Issue

  • When combined with the Batcher Policy, the Auth Caching Policy is not behaving as expected:
    • In Allow mode, the gateway does not authorize new requests if the backend-listener component is unavailable.
    • In Strict mode, denied requests do not cause the corresponding cache entries to be invalidated.

Environment

  • Red Hat 3scale API Management Platform (3scale)

    • 2 (On Premise)
    • SaaS
  • APIcast Auth Caching Policy

    • Allow mode
    • Strict mode
  • APIcast Batcher Policy

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In