-
Epic
-
Resolution: Done-Errata
-
Blocker
-
rhos-18.0.0
-
None
-
TLS Everywhere in the horizon operator
-
5
-
False
-
-
False
-
Not Selected
-
Committed
-
No Docs Impact
-
To Do
-
RHOSSTRAT-282 - TLS-everywhere
-
horizon-operator-bundle-container-1.0.0-15
-
Committed
-
Committed
-
0% To Do, 0% In Progress, 100% Done
-
-
Enhancement
-
Done
-
Regression Only
-
-
-
5
-
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
- links to
-
RHBA-2024:135531 OpenStack Operators