consul/agent/connect/ca
Daniel Nephin 608597c7b6 ca: relax and move private key type/bit validation for vault
This commit makes two changes to the validation.

Previously we would call this validation in GenerateRoot, which happens
both on initialization (when a follower becomes leader), and when a
configuration is updated. We only want to do this validation during
config update so the logic was moved to the UpdateConfiguration
function.

Previously we would compare the config values against the actual cert.
This caused problems when the cert was created manually in Vault (not
created by Consul).  Now we compare the new config against the previous
config. Using a already created CA cert should never error now.

Adding the key bit and types to the config should only error when
the previous values were not the defaults.
2022-02-03 17:21:20 -05:00
..
common.go Format certificates properly (rfc7468) with a trailing new line (#10411) 2021-06-30 20:48:29 -04:00
mock_Provider.go ca: update MockProvider for new interface 2022-01-27 12:51:35 -05:00
provider.go ca/provider: remove ActiveRoot from Provider 2022-01-27 13:07:37 -05:00
provider_aws.go ca/provider: remove ActiveRoot from Provider 2022-01-27 13:07:37 -05:00
provider_aws_test.go ca/provider: remove ActiveRoot from Provider 2022-01-27 13:07:37 -05:00
provider_consul.go ca/provider: remove ActiveRoot from Provider 2022-01-27 13:07:37 -05:00
provider_consul_config.go add root_cert_ttl option for consul connect, vault ca providers (#11428) 2021-11-02 11:02:10 -07:00
provider_consul_test.go ca/provider: remove ActiveRoot from Provider 2022-01-27 13:07:37 -05:00
provider_test.go add root_cert_ttl option for consul connect, vault ca providers (#11428) 2021-11-02 11:02:10 -07:00
provider_vault.go ca: relax and move private key type/bit validation for vault 2022-02-03 17:21:20 -05:00
provider_vault_test.go ca/provider: remove ActiveRoot from Provider 2022-01-27 13:07:37 -05:00
testing.go fix misleading errors on vault shutdown 2021-12-08 18:42:52 -05:00