Allows for scenario where user is supplying their own CA Signed x509 certs and priv keys and we are not generating those in the framework. Expecting that each host has a directory, defined in variable "tls_presigned_certs": e.g. /etc/pki/certs, which contains: PEM format x509 signed cert, named .pem RSA style private key that is encrypted, named .key Passphrase for key is supplied by variable "tls_key_password" The Public CA certs of Issuer, root (and any intermediates) are expected to be on the controller host, defined by variable "tls_ca_certs" which has a list of CA certs. example:
tls_ca_certs:
Allows for scenario where user is supplying their own CA Signed x509 certs and priv keys and we are not generating those in the framework. Expecting that each host has a directory, defined in variable "tls_presigned_certs": e.g. /etc/pki/certs, which contains: PEM format x509 signed cert, named.pem RSA style private key that is encrypted, named .key Passphrase for key is supplied by variable "tls_key_password" The Public CA certs of Issuer, root (and any intermediates) are expected to be on the controller host, defined by variable "tls_ca_certs" which has a list of CA certs. example:
tls_ca_certs: