CertificateNotTrustedFault
An CertificateNotTrusted fault is thrown when an Agency's configuration contains OVF package URL or VIB URL for that vSphere ESX Agent Manager is not able to make successful SSL trust verification of the server's certificate.
Reasons for this might be that the certificate provided via the API ovfSslTrust and vibSslTrust or via the script /usr/lib/vmware-eam/bin/eam-utility.py
- is invalid.
- does not match the server's certificate.
If there is no provided certificate, the fault is thrown when the server's certificate is not trusted by the system or is invalid - @see ovfSslTrust and vibSslTrust. To enable Agency creation 1) provide a valid certificate used by the server hosting the ovfPackageUrl or vibUrl or 2) ensure the server's certificate is signed by a CA trusted by the system. Then retry the operation, vSphere ESX Agent Manager will retry the SSL trust verification and proceed with reaching the desired state.
This structure may be used only with operations rendered under /eam.
Since: vEAM API 8.2
{
"_typeName": "string",
"faultCause": "MethodFault Object",
"faultMessage": [
{
"_typeName": "string",
"key": "string",
"arg": [
{
"_typeName": "string",
"key": "string",
"value": {
"_typeName": "string"
}
}
],
"message": "string"
}
],
"url": "string"
}The URL that failed the SSL trust verification.