The NSX Manager Web-UI has a default timeout of 1800 seconds. i.e., the NSX Manager UI will time out after 30 minutes of inactivity. This timeout looks reasonable for a production deployment, but since security is not an issue in lab settings, you might want to change it to a little bit higher. On top of that, it is annoying to get kicked out of the UI after 30 minutes of idle session.
In this post, I will demonstrate how you can change the timeout value.
Run the command get service http to see the currently configured value:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
compute-nsxt01> get service http Service name: http Service state: running Logging level: info Session timeout: 1800 Connection timeout: 30 Client API rate limit: 100 requests/sec Client API concurrency limit: 40 connections Global API concurrency limit: 199 connections Redirect host: (not configured) Basic authentication: enabled Cookie-based authentication: enabled |
Run the command set service http session-timeout 0 to fully remove the session timeout.
You can run the get command again to verify that the settings have taken effect.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
compute-nsxt01> set service http session-timeout 0 compute-nsxt01> get service http Mon Feb 12 2024 UTC 04:30:11.833 Service name: http Service state: running Logging level: info Session timeout: 0 Connection timeout: 30 Client API rate limit: 100 requests/sec Client API concurrency limit: 40 connections Global API concurrency limit: 199 connections Redirect host: (not configured) Basic authentication: enabled Cookie-based authentication: enabled |
Note: The service is restarted upon executing the set command, and it can take a few seconds for the newly configured timeout values to take effect.
Setting default session timeout to a custom value
The timeout can also be customized by specifying a value in seconds. For instance, use the command set service http session-timeout 300 to set the timeout to five minutes.