Prime Infrastructure provides two settings that control when and how idle users are automatically logged out:

• User Idle Timeout—You can disable or configure this setting, which ends your user session automatically when you exceed the timeout. It is enabled by default and is set to 10 minutes. The User Idle Timeout value must be lesser or equal to the Global Idle Timeout vlaue.
• Global Idle Timeout—The Global Idle Timeout is enabled by default and is set to 10 minutes. Only users with administrative privileges can disable the Global Idle Timeout setting or change its time limit.

Note	Prime Infrastructure will log out the idle user based on the lesser Timeout value.

You may find it useful to disable the user idle timeout feature if, for example, you are an Operations Center user experiencing sudden log-offs, due to idle sessions, with one or more Prime Infrastructure instances managed by Operations Center. For details, see the section Disable Idle User Timeouts for Operations Center in the chapter Set Up the Prime Infrastructure Server in the Cisco Prime Infrastructure Administrator Guide. .

Irrespective of the customer disabling the "Logout all idle users" in system settings and / Or disabling the "Logout idle user" in the Root user my preference setting, the session will ultimately be timed out once the web-server's session time out is reached. This is essentially to maintain the security posture. For more guidelines on increasing/decreasing the session time out, see https://owasp.org/www-community/Session_Timeout

Note	Session will be timed out only if it is inactive, whereas active user sessions are not timed.

To change the timeout settings, follow these steps:

By default, client sessions are disabled and users are automatically logged out after certain period of inactivity. This is a global setting that applies to all users. To avoid being logged out during the installation, it is recommended to disable automatic logout of idle users in the system settings using the following procedure.

Note	The Global Idle Timeout setting overrides the User Idle Timeout setting. To configure Global Idle Timeout settings, see .

Irrespective of the customer disabling the "Logout all idle users" in system settings and / Or disabling the "Logout idle user" in the Root user my preference setting, the session will ultimately be timed out once the web-server's session time-out is reached. This is essentially to maintain the security posture. For more guidelines on increasing/decreasing the session time-out, see https://owasp.org/www-community/Session_Timeout

Note	Session will be timed out only if it is inactive whereas active user sessions are not timed.

Prime Infrastructure lets you change the default number of entries displayed in some lists. The Items Per List setting affects the number of entries displayed on the monitoring pages for:

• APs
• Controllers
• Site Maps
• Mesh
• CleanAir

The Items Per List setting does not apply to Network Devices, alarms and events, configuration archive, software image management, or configuration.

An average of 50 items will be shown on a given page.

Prime Infrastructure provides two settings that control when and how idle users are automatically logged out:

• User Idle Timeout—You can disable or configure this setting, which ends your user session automatically when you exceed the timeout. It is enabled by default and is set to 15 minutes.

• Global Idle Timeout—The Global Idle Timeout setting overrides the User Idle Timeout setting. The Global Idle Timeout is enabled by default and is set to 15 minutes. Only users with administrative privileges can disable the Global Idle Timeout setting or change its time limit.

By default, client sessions are disabled and users are automatically logged out after 15 minutes of inactivity. This is a global setting that applies to all users. For security purposes, you should not disable this mechanism, but you can adjust the timeout value using the following procedure. To disable/change the timeout for an idle user, see Disable Idle User Timeout.