Legacy SSL configration options do not have effect
Bug #1864805 reported by
José Pekkarinen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Barbican Charm |
Fix Released
|
High
|
José Pekkarinen | ||
Bug Description
Hi,
It's found that the charm provides config options for tls enpoint setup,
concretely ssl_cert and ssl_key, though it misses the code that produces
apache2 configuration for the tls endpoint to happen. An MP is open to
produce this configuration.
Thanks!
José.
Revision history for this message
| Frode Nordahl (fnordahl) wrote | #1 |
| summary: |
- Missing call for ssl endpoint configuration + Legacy SSL configration options do not have effect |
| Changed in charm-barbican: | |
| milestone: | none → 20.05 |
| importance: | Undecided → High |
| assignee: | nobody → José Pekkarinen (jose-pekkarinen) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to charm-barbican (master) | #2 |
| Changed in charm-barbican: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to charm-barbican (stable/20.02) | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on charm-barbican (stable/20.02) | #4 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to charm-barbican (stable/20.02) | #5 |
| Changed in charm-barbican: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The ssl_* configuration options are brought in from ``layer-openstack`` and unfortunately there was a missing call to act on them being set in the charm.
I would like to remind everyone that the preferred approach to TLS enablement of OpenStack deployments is through the use of the certificates relation to vault.