Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-5882

TLS everywhere in Horizon operator

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • rhos-18.0.0
    • rhos-18.0.0
    • horizon-operator
    • None
    • TLS Everywhere in the horizon operator
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • OSPRH-450TLS-everywhere
    • Not Selected
    • Committed
    • No Docs Impact
    • To Do
    • OSPRH-450 - TLS-everywhere
    • horizon-operator-bundle-container-1.0.0-15
    • Committed
    • Committed
    • 0% To Do, 50% In Progress, 50% Done
    • 5
    • UV; UI
    • Approved

      Definition of Done (for development)

      • By implementing <configuration>, a RHOSO 18 deployment is stood up with Horizon correctly configured to provide client-side TLS connectivity, and connect to the back-end via TLS
      • On the client side, all the response headers are configured for maximum security, while still allowing the application to run correctly.
      • Patches proposed and merged into horizon-operator (not necessarily into openstack-operator)
      • Tests developed and implemented to validate the presence of the headers

      Acceptance Criteria (for validation)

      • Horizon delivers content via HTTPS, with secure headers
      • Horizon interacts with OpenStack via HTTPS
      • Integration tests pass

            rhn-engineering-rdopiera Radomir Dopieralski
            rhn-engineering-rdopiera Radomir Dopieralski
            rhos-dfg-ui
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: