Hello,
We have 7.13 connection servers. I'm trying to figure out how to extend the admin web session timeout. I've tried the logical thing by changing my preferences as below but the time out is still less than 5 minutes. Extremely frustrating to use. This occurs for everyone. I assume it is a setting on the connection servers?
Thanks Fish!
@vmrulz ,
Where did you find this setting. If I check my 7.13 connection server, the settings is under "Settings" - "Global Settings" - "General Settings" where you have "Connetion Server Session time out". My screen however doesn't look like yours:
Sorry, just found out where you set the timeout: using the "settings" button on top of the page. This is an override of the global setting for the current session only apparently. Never used it. Probably it's taking the smallest timeout of both settings, not sure about that.
Try changing it using the global settings.
Try the below one. Enabling automatic updates on the View Connection server
https://kb.vmware.com/s/article/1034033
This doesn't seems to be correct. I have automatic updates enabled and timeout on 15 minutes. This is the screen I get when 14 minutes have passed:
This is on a 2106 connection server, but the same happens on 7.13. (just tested it)
Thank you I think we'll try doing the web-inf file since we don't have want to automatically update our infra.
Ron
Remember that this setting will be lost when you upgrade your Horizon environment.
just asking as i still haven't found any valid workaroudn 7 fix.
Even within version 8 ( 2209 ) we have the problem that admins will be kicked out after 10 minutes, even if we configured with global settings
Hi @ET0099,
Are the admins directly pointing to a Connection Server or do they access the Horizon Console via a load balancer?
I'm pointing directly to the connection server and the stupid console times out even if you are actively using it.
Started happening after upgrading to 2209. Really annoying.
Agreed this is the only applicaiton I use that the timeout cannot be managed regardless of what you set it to. VMware doesn't seem to think it is a problem. Doesn't matter whether you connect directly to a connection server or via Load balancer.
We are on 2209 now and still experiencing this stupidity.
I have the same issue after upgrading to 2209, except my timeout is always 8 hours even though I have it set to 12 hours.
It used to work fine in Horizon 2203.
I upgraded to 2209 in December and it's been broke since. Haven't tried upgrading to a newer version yet... but 2209 definitely has some bugs with the Horizon Admin Console Timeout setting.
I work a 10 hour day and I always have to reauthenticate to Horizon Admin console at 2:30pm because of the 8 hour timeout. :')
The sad part is that you are actively working on something in the console and the stupid thing logs you off.
I actually made my timeout worse looking into this yesterday.
I set the timeout on my profile to 720 minutes by clicking the gear in the upper right and now it always logs me off every 9 minutes.
Wish I knew how to fix it!
Did you also set a higher value in the API session timeout? This is by default 10 minutes, so that could be the reason you're logged off after approx. 9 minutes.
No, I'll give this a try. I wasn't aware the API session timeout applied to the admin console. (I thought it was for interacting with the console without being on the web.. through straight APIs.)
I'll give it a try now.
::comes back after trying it::
WELL, that's odd. Changing the API session timeout from 10 to 4320 seems to have resolved the issue. (Why does this affect admin logins? I'm using the web browser and not APIs to do work in the Horizon Console... I've never had to change this value from the default of 10 minutes in 2203 and older...)
Time to dial the number back down to my original value of 720 and see what happens!
Thanks for the suggestion!
Well, the console actually does API calls for all the work...
Very weird! They should just combine those 2 into one setting then instead of having one called "Horizon Console Session Timeout" and "API Session Timeout" :')
Thank you again, you rock.
They atleast added this tool tip which explains that the API timeout is the upper limit. I don't understand the need for both settings, it just adds to the confusion. I'm doing a POC of Horizon 8 now and it's been driving me insane that i was getting logged out after 10 minutes while I was ACTIVELY USING IT.