- Advertisement -
HomeVirtualizationVMwareConfiguring the vSphere Web (HTML5) Client Session Timeout for VCSA 6.7

Configuring the vSphere Web (HTML5) Client Session Timeout for VCSA 6.7

WHAT:

By default, a VMware vSphere Web Client 6.7 session terminates after 120 minutes of idle time. You may want to configure/edit the vSpehre Client idle sessions to:

  • Improve the login security of productions environments and reduce resources consumption on VCSA. Ensuring that the sessions automatically logout after a certain period of time.
  • Avoid the session to constantly logout. Probably you are just starting a new deployment that may require a bit of time to configure or due to the use of a testing lab.

In my case, I want to set the web client to never time out.

HOW:

In the past, this could be done directly from the c# client. In the current HTML5 client GUI, this option is not available, it is only available on the Flex client, but even if you attempt to change this value from the Flex client from the UI, is not going to work.

Note: I am happy that later this year vSphere 6.7 will release its first update, it is supposed to fully support the new and sexy HTML5 client.

For HTML5 client

  1. Open an SSH session on your VCSA
  2. Type the following commands and hit enter in this order:
shell.set --enabled True
shell
cd /etc/vmware/vsphere-ui/
vi webclient.properties
p23 Image03.1

@ vi Editor:

- Advertisement -
  1. Navigate to “session.timeout = 120”. Where 120 is the default value in minutes.
p23 Image04
  1. Hit insert key to edit.
  2. Delete the default value and enter 0 to never log out the sessions. Or enter the desired value in minutes.
  3. Press Esc key.
  4. Type :wq to write and quit the vi Editor. The new timeout is now set to 0 (in my case)
  5. Stop and start the vSphere Web Client service:
service-control --stop vsphere-ui
service-control --start vsphere-ui

Resources:

https://kb.vmware.com/s/article/2040626
Juan Mulford
Juan Mulford
I have been active in IT for over fourteen years now. I am a solutions architect, working with storage, virtualization, and VDI solutions. For the past ten years, I have been living and working in Taiwan.

4 COMMENTS

  1. You need to use double dashes, like this:
    service-control –-stop vsphere-ui
    service-control –-start vsphere-ui

Leave a Reply

- Advertisement -

Popular Articles

mulcas.com-Raspberry-Pi

Raspberry Pi OS in a Virtual Machine with VMware

4
Although the Raspberry Pi OS is designed and optimized for the Raspberry Pi module, it is possible to test and use it without its hardware, with VMware. This solution can be useful if you are a developer (or just a curious guy) and don't have a Raspberry Pi module with you
Unable to delete inaccessible datastore

Unable to delete an "inaccessible" datastore

7
I was switching my storage array, so I migrated the VMs from that old datastore/storage to a new datastore/storage. The old datastore was shared by 3 ESXi hosts, no cluster. After migrating the VMs and unmount/delete the datastore, it was still presented in two of the ESXi hosts and was marked as inaccessible.
This is not a valid source path / URL

This is not a valid source path / URL - SourceTree and Gitlab

0
I have been working on a project with a friend who set up a repository in Gitlab but even though I was able to view all projects on it, I couldn’t really join the repository. I was using SourceTree and Gitlab.
mulcas.com-VMware-OVF-Tool

How to export a Virtual Machine using the VMware OVF Tool

9
The VMware OVF Tool is implemented by VMware for easily importing and exporting virtual machines in Open Virtualization Format (OVF) standard format. Here, I want to show you how to download and install it, and then how to use it from a Windows machine.
Couldn't load private key - Putty key format too new

Couldn't load private key - Putty key format too new

5
couldn't load private key - Putty key format too new.” This issue happens when you use PuTTygen to generate or convert to a ppk key. Here is how to fix it. 
- Advertisement -

Recent Comments