ive encounter with the same issue in my envieroment,the only solution ive found was:
- disable the View desktops in the IDM
- enable the view desktops in IDM
- in the connection server change the name of the server in the metadata to the FQDN of the IDM
- change back to the hostname
you will ge a popup of the certificate
again this was asepcific case ive had in the envieroment caused by change of certificate in the view server
Do i disable the View D in the Horizon Catalog? I already disabled it and then readded it and re authed the Certs. Can you give me a bit more detail on 3. and 4? Im not sure where to change the name of hte server in the metadata to the FQDN of the IDM.
did u manage to fix this issue.
Facing the same.
I am also getting the same error when launching the application from vDIM portal.. Did you manage to resolve this..
Hi, one issue I found out was, connection server fqdn should be same the actual host name of the connection server.
say your actual connection server host name is connectionsrv.doamin.local. You should use the same when configuring VIDM.
In my environment our doamin had a underscore like my_domain.local. To workaround this i created a dns entry for the connection server ip in DNS as connectionsrv.mydomain.local (without underscore). It doesnt work. faced the same issue
try check the value in table FederationArtifacts of the VIDM database. It will give you more insight.
If you use default postgres DB use the below command to export the content to text file
export PGPASSWORD=cat /usr/local/horizon/conf/db.pwd
/opt/vmware/vpostgres/9.2/bin/psql -U postgres saas
saas=# \o FedTableContents.txt
saas=# select * from "FederationArtifacts";
We are having this issue in our environment as well. It seems like after 5-10 app launches this messages pops up. It isn't always possible to recreate though. After the pop-up you have to close the Horizon client and relaunch. I believe this is based on the Horizon setting of forcing 3rd party logons, or prohibiting logons directly thru the client and forcing them thru the IDM portal. Even though this setting isn't check it seems to be true in some cases.
VMware claims they are not aware of this issue when we brought it up to them. Might be time for a ticket if I can find a way to reproduce it while they are on the call.
Could you please check Time on all Connection server and vIDM appliances. If time is not in Sync you will get such login issues.
Yes, all servers are perfectly in sync. I have a ticket open and the tech is requesting we reboot all of the servers. But I can't keep doing that every couple weeks because no one can find the root cause of the problem.
We are having the same issue. Were you able to find the root cause.
We still have not found a root cause for this. Rebooting the connection servers and appliances has resolved the issue, for now. But I suspect it will pop-up again in the future. So far VMware has not been able to find anything in the logs that could be causing this problem.
This issue has popped up again after only 2 weeks of the servers running. I have reopened the ticket with VMware. I will let you know what they say.