WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / vSphere / Configuring New vSphere Web Client Session Timeout

Configuring New vSphere Web Client Session Timeout

09.10.2012 by William Lam // 5 Comments

Just like you could in the old vSphere C# Client, users can also configure a session timeout for the new vSphere Web Client in the latest release of vSphere 5.1. This not only ensures that idle sessions automatically disconnect after a certain period of time but also helps reduce the resources consumed on the vCenter Server as each session allocates a certain amount of resources.

To configure the session timeout, you will need to login to the server running the vSphere Web Client service (which is usually your vCenter Server) and find the webclient.properties file and change the default timeout and then restart the vSphere Web Client service. For the VCSA, the default timeout value is 120 minutes and I assume it is the same default for the Windows vCenter Server.

Step 1 - Locate the webclient.properties file:

    VCSA 5.x

/var/lib/vmware/vsphere-client/webclient.properties

    VCSA 6.x

/etc/vmware/vsphere-client/webclient.properties

    Windows vCenter Server 5.x

%ALLUSERPROFILE%\VMware\vCenterServer\cfg\vsphere-client\webclient.properties

    Windows vCenter Server 6.x

%ALLUSERPROFILE%\VMware\vSphere Web Client\webclient.properties

Step 2 - Un-comment and change session.timeout value to desired value:

session.timeout = 120

Step 3 - Restart the vSphere Web Client Service:

/etc/init.d/vsphere-client restart

You will need to restart the vSphere Web Client service for the changes to go into effect. For the Windows vCenter Server, just restart the vSphere Web Client service and for the VCSA, run the above command.

In my lab, I configured the time out to be 1 minute, once the session has gone idle for the configured period, you will automatically be logged out and brought back to login page with the following message:

 

More from my site

  • Dude, Where's My vCenter Server 5.1 Components Installed At?
  • How to Add/Remove vCenter SSO Identity Sources Using the Command-Line for Windows vCenter Server & VCSA
  • Configuring Additional VCSA 5.1 as vSphere Web Client Servers
  • Configuring Additional Windows vSphere Web Client 5.1 Servers
  • vCloud Director 5.1 Introduces "Open in vSphere Web Client" & Task Correlation ... Awesomeness!

Categories // vSphere, vSphere 5.5, vSphere 6.0, vSphere Web Client Tags // session, sso, timeout, vSphere 5.1, vsphere web client

Comments

  1. *protectedVenti says

    11/20/2015 at 11:52 am

    Hi William,
    I think that for Vsphere 6.0 U1 the location on this file on VCSA is in this folder:
    /etc/vmware/vsphere-client

    Can you confirm that this is the correct ?

    Thanks

    Reply
    • William Lam says

      11/22/2015 at 6:56 am

      Thanks for the comment. Yea, the path has changed in 6.x. I've updated the article to reflect both VCSA & Windows VC

      Reply
  2. *protectedRoss says

    04/26/2016 at 4:58 am

    Path updated to: \ProgramData\VMware\vCenterServer\cfg\vsphere-client in windows.

    Reply
  3. *protectedAlpesh says

    08/08/2018 at 3:25 pm

    How do we automate this? This is one of the stig setting that needs to be updated. We have automated script to install vSphere 6.7 and trying to find out a way where I can change this setting during installation or after installation using powershell or powerCli or using other ways. I will appreciate any insight to this issue. Thank you.

    Reply
    • *protectedlkj345klj345 says

      12/19/2018 at 6:51 am

      I'm looking for the same, did you manage to automate it?

      Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025
  • vCenter Server Identity Federation with Kanidm 04/10/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025