Closed saltiyazan closed 3 months ago
In addition to this, the logic for checking if the old CA certificate matches is incorrect.
In the code above, we return None
if the cert doesn't match.
In the caller [above], we return early if the return value is None
, so we return before updating the certificate
Bug Description
When the common name used to configure the PKI engine in the charm changes, the PKI role is not updated to allow creating certificates for the new common name
To Reproduce
juju deploy vault-k8s
juju deploy self-signed-certificates
juju integrate vault:tls-certificates-pki self-signed-certificates
juju deploy tls-certificates-requirer
juju config vault common_name=mydomain.com
juju config tls-certificates-requirer common_name=example.com
juju config vault common_name=example.com
juju integrate tls-certificates-requirer vault:vault-pki
Environment
Juju 3.4 and Vault-k8s 1.15 beta
Relevant log output
Additional context
No response