EamCertificateNotTrusted
The agent Virtual Machine deployment or agent VIB module installation cannot be done, because vSphere ESX Agent Manager is not able to make successful SSL trust verification of the server's certificate, when establishing connection to the provided ovfPackageUrl or vibUrl.
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 issue is raised when the server's certificate is not trusted by the system or is invalid - @see ovfSslTrust and vibSslTrust. To remediate the agent Virtual Machine deployment or agent VIB module installation 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 resolve this issue, 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",
"key": 0,
"description": "string",
"time": "string",
"agency": {
"_typeName": "string",
"type": "string",
"value": "string"
},
"agencyName": "string",
"solutionId": "string",
"solutionName": "string",
"agent": {
"_typeName": "string",
"type": "string",
"value": "string"
},
"agentName": "string",
"host": {
"_typeName": "string",
"type": "string",
"value": "string"
},
"hostName": "string",
"url": "string"
}The URL that failed the SSL trust verification.