Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-22817

Dont cache nack responses from compliance service

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      • When a user receives a non-compliant response during the compliance check in the gateway, that response should not be cached. Compliant checks will continue to be cached for 24 hours.
      • If my account is non-compliant, and is unlocked/unblocked by the legal team (assuming I should not actually be blocked as non-compliant), I should immediately regain access to all console.redhat.com APIs.
      Show
      When a user receives a non-compliant response during the compliance check in the gateway, that response should not be cached. Compliant checks will continue to be cached for 24 hours. If my account is non-compliant, and is unlocked/unblocked by the legal team (assuming I should not actually be blocked as non-compliant), I should immediately regain access to all console.redhat.com APIs.
    • Unset
    • No
    • Platform A&M Sprint 54, Platform A&M Sprint 55

      In 3scale when we ping export compliance service for user compliance we cache all responses. We want to change this to only cache "OK" responses. If a user is blocked/non-compliant, that can get resolved manually very quickly (few minutes). We want that unblocking to reflect in 3scale right away instead of having to wait for the cache entry to expire.

              rh-ee-dagbay Daniel Agbay
              rh-ee-dagbay Daniel Agbay
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: