When using certificates, we should:
* Validate that the correct name is mentioned in the certificate
* Validate that the key and certificate match
* That we open the correct port
* That we close the correct port
* Validate that the correct encoding is used
We explicitly don't check the certificate chain or CA, as that is
something that is up to the endpoint (snapd) to validate and with custom
certificates there is a change that we don't have all the needed
information.
When using certificates, we should:
* Validate that the correct name is mentioned in the certificate
* Validate that the key and certificate match
* That we open the correct port
* That we close the correct port
* Validate that the correct encoding is used
We explicitly don't check the certificate chain or CA, as that is
something that is up to the endpoint (snapd) to validate and with custom
certificates there is a change that we don't have all the needed
information.
Since the tools `store-admin` will already output the data in the
correct format for juju config to consume, there is no need for the end
user to do any manipulation. So the documentation is updated to reflect
this.
Since the tools `store-admin` will already output the data in the
correct format for juju config to consume, there is no need for the end
user to do any manipulation. So the documentation is updated to reflect
this.