Horizon adapter in vrops failed, cannot log in and Horizon does not trust Aria Operations
Article ID: 323492
Updated On:
Products
Issue/Introduction
the purpose of this knowledge base article is to provide a possible solution to the issue with Vrops 8.12 and later not able to connect to Horizon CS
Symptoms:
vrops 8.12.1 (21952151) Horizon 8.9.0 build - 21507980 vRealize Operations Management Pack for Horizon 2.5.1.21222817 VROPs has lost connectivity to horizon, and trying to reconnect gives an error about bad username/password.
The credentials are correct when logging in directly. Recent lines from Horizon Adapter log file
6612] 2022-03-02T16:55:06,259+0000 ERROR [Collector worker thread 24] (3094) com.vmware.vrho.adapter.utils.helpers.LoginHelper.testHorizonVlsiSdkConnection - Testing Horizon Vlsi Sdk Connection Failed. Reason: Authentication failed: LogonUser FAILED, error=1326 (The user name or password is incorrect.) [6613] 2022-03-02T16:55:06,259+0000 ERROR [Collector worker thread 24] (3094) com.vmware.vrho.adapter.HorizonAdapter.onCollect - Error encountered during collection : Invalid User Credential for Horizon Vlsi [6614] java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_312] [6624] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_312] [6625] Caused by: com.vmware.vim.binding.vmodl.fault.SecurityError: Authentication failed: LogonUser FAILED, error=1326 (The user name or password is incorrect.) [6626] at sun.reflect.GeneratedConstructorAccessor529.newInstance(Unknown Source) ~[?:?] [6627] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_312] [6628] at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_312] [6629] at java.lang.Class.newInstance(Class.java:442) ~[?:1.8.0_312] [6630] at com.vmware.vim.vmomi.core.types.impl.ComplexTypeImpl.newInstance(ComplexTypeImpl.java:174) ~[view-api-public-20.17686435.jar:?] [6631] at
2024-12-02T13:54:37,315+0000 WARN [Collector worker thread 15] (885) com.vmware.vrho.adapter.utils.helpers.vlsi.HorizonRequestRetryCallback.retry - RequestRetryCallback handling Exception: com.vmware.vim.vmomi.client.exception.SslException: org.bouncycastle.tls.TlsFatalAlert: certificate_unknown(46)
HorizonAdapter_885.log.6:2024-11-23T16:29:27,746+0000 ERROR [Collector worker thread 20] (885) com.vmware.vrho.adapter.utils.helpers.LoginHelper.testAllHorizonConnections - Testing Horizon Connection Failed. Reason: org.bouncycastle.tls.TlsFatalAlertReceived: handshake_failure(40)Environment
VMware Aria Operations 8.12.x and later.
Cause
The horizon adapter only works if the name provided in the integration matches with the hostname defined in the SSL certificate. Horizon must trust Aria Operations for data collection to start.
Resolution
The problem with connecting vRops to Horizon CS is caused by having the external host name configured for the connection server instead on having the internal host name.
Please try the following work arounds:
1. The horizon adapter only works if the name provided in the integration matches with the hostname defined in the SSL certificate.
2. Try using the internal hostname in vRops integration with Horizon.
3. If the issue is not resolved, open a case with Omnissa to resolve the certificate/trust issue between Aria Operations and Horizon. Additional Information
connection from vRops to Horizon CS is not established, hence no data collection happens
Feedback
