Major - Who is the customer behind the request?
-
- Account Name: Banco do Brasil S.A
-
- TAM customer: yes
-
- CSM customer: yes
-
- Strategic: yes
- What is the nature and description of the request?
- The customer is facing a rate limit problem described on https://access.redhat.com/support/cases/#/case/03453891. But the suggestion of using the Auth Caching policy does not resolve the problem because any oscillation of the backend listener will result in an 403/401 error
- Why does the customer need this? (List the business requirements here)
-
- The customer needs to guarantee that using this policy the rate limit configured will be followed. And the suggestion was to tryed use this policy.
- How would the customer like to achieve this? (List the functional requirements here)
-
- Using this approach, they need to return a 200 status to the requester when the backend listener returns an error. Or create a new option within the policy that discovers when the backend listener is returning an error and then returns a 200 status code.
- For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
-
- To test it in the interface it should be configured this policy with “none” option selected. After that when the backend listener returns an error it should send a status 200 to the requester.
- Is there already an existing RFE upstream or in Red Hat Bugzilla?
-
- No
- Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
- They need it in the next releases (for the next 6 or 9 months).
- Is the sales team involved in this request and do they have any additional input?
-
- The sales team is involved, no additional input.
- List any affected packages or components.
- Backends, products, application-plan
- Would the customer be able to assist in testing this functionality if implemented?
-
- Yes
