Insecure certificate requests
Bug #1663757 reported by
Adrian Otto
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
High
|
yatin | ||
Pike |
Fix Released
|
Undecided
|
Unassigned | ||
Queens |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In October, our team merged a patch to solve a problem with certificate transfers between cluster nodes and the Magnum API.
https:/
The problem for this resolution is that it causes Bandit tests to fail, as explained here:
http://
Please re-implement a solution that uses TLS connections by default, but optionally allows operators to relax certificate verification or use an insecure HTTP transport if their deployments require those workarounds.
Changed in magnum: | |
assignee: | nobody → Vijendar Komalla (vijendar-komalla) |
Changed in magnum: | |
status: | Triaged → In Progress |
Changed in magnum: | |
assignee: | Vijendar Komalla (vijendar-komalla) → Kirsten G. (oikiki) |
Changed in magnum: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Adding the CA cert to each cluster node at create time would allow for proper operation. We could allow this to be configured in the cluster driver(s).