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

[export-service] export api requests return 400 when using cert auth

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • None
    • Export
    • False
    • Hide

      None

      Show
      None
    • False
    • Unset
    • None

      Note: Similar to and perhaps a dup of:

      https://issues.redhat.com/browse/RHCLOUD-34799

       

      When I make export service api requests using cert auth, the response is always 400.  Compounding this is the lack of an error message, so I don't know what's wrong.  For example, this is the response:

      HTTP response headers: HTTPHeaderDict({'Server': 'openresty', 'Content-Type': 'application/json; charset=utf-8', 'Content-Length': '26', 'x-rh-insights-request-id': '7ddc906f40c041c9b569be22ccfd46bc, 7ddc906f40c041c9b569be22ccfd46bc', 'x-content-type-options': 'nosniff', 'Date': 'Thu, 22 Aug 2024 22:09:31 GMT', 'Connection': 'close', 'Set-Cookie': 'e15dd7c1deaec3a6b67fca153d520b0b=8b064d6c9206ef011040c41645bde6bb; path=/; HttpOnly; Secure; SameSite=None', 'x-rh-edge-request-id': '28b354a', 'x-rh-edge-reference-id': '0.9ece4917.1724364571.28b354a', 'x-rh-edge-cache-status': 'NotCacheable from child', 'X-Frame-Options': 'SAMEORIGIN', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'})
HTTP response body: {"message":{},"code":400}

      Note, the message is empty.
       
      Looking at the pod logs, the message is also empty:
       

      {"level":"info","@timestamp":"2024-08-22T22:02:46.6131Z","caller":"logger/logger.go:95","msg":"","protocol":"HTTP/1.1","request":"GET","path":"/api/export/v1/exports","latency":0.000137583,"status":400,"size":26,"request_id":"93916e47ac7e4858863e119d16b2ae81"}

              rhn-support-dehort Derek Horton
              msager@redhat.com Michael Sager
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: