Symptoms:
The integration failed because Aria Operations re‑validated SSL trust (likely after a service restart or patch). The vRNI certificate itself is unchanged, but Aria Ops no longer trusts the custom certificate chain, causing adapter authentication to fail with a 401 error.
Untrusted certificate found.
Certificate Thumbprint: ##############################################
Issued to: EMAILADDRESS=#########.##########@########.com, C=FR, ST=IDF, O=###### Inc., CN=#####################.net
Issued by: CN=###### Certificate Authority ######, OU=####### ###, O="#######, Inc.", C=US
Expires: DD MM YYYY ##:##:## TIMEZONE
Test Connection failed. Error Code 401 Unauthorized. Please enter correct credentials and try again.
Aria Operations 8.18.x
Sometimes, simply clicking "Accept" on an untrusted leaf certificate during the adapter configuration does not persist through a service restart, especially if the Root CA is missing. We need to add the Custom Certificate chain to Aria Operations global trust store.
Export the Root Certificate and any Intermediate Certificates for the Custom Certificate Authority in Base64 PEM format (.cer or .pem).
Import to Aria Operations:
Log in to the Aria Operations UI as an administrator.
Navigate to Administration > Certificates > Trusted Certificates (Depending on the exact UI view, it may be under Administration > Support > Trusted Certificates).
Click Import (or Add).
Upload the Root CA and Intermediate CA certificates.
Note: Ensure to upload the Root CA first, followed by the Intermediate.
Once the certificates are globally trusted:
Go to Data Sources > Integrations > Accounts in Aria Operations.
Select the VMware Aria Operations for Networks adapter instance and click Edit.
If a prompt appears to review and accept the certificate, click Accept. The connection should now validate successfully.