Set User Preferences
Prime Infrastructure provides user preference settings that allows you to modify how information is displayed.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Prime Infrastructure provides user preference settings that allows you to modify how information is displayed.
To change your user preferences, click the Settings icon (the gear icon on the right side of the menu bar) and choose My Preferences and change the settings shown on the My Preferences page.
Prime Infrastructure provides two settings that control when and how idle users are automatically logged out:
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:
Step 1 |
Click the Settings icon and choose My Preferences. |
Step 2 |
Under User Idle Timeout:
|
Step 3 |
Click Save. You will need to log out and log back in for this change to take effect. 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. |
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 CiscoPrime 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 |
Step 1 |
Choose , then choose . |
Step 2 |
In the Global Idle Timeout area, uncheck the Logout all idle users check box and click Save. |
Step 3 |
Click at the top right of web GUI window and choose My Preferences. |
Step 4 |
In the User Idle Timeout area, uncheck the Logout idle user check box and click Save. If you need to change the idle timeout value, then select Logout idle user check box and from the Logout idle user after drop-down list, choose one of the idle timeout limits. (But this cannot exceed the value set in the Global Idle Timeout settings.) |
Step 5 |
Click Save. You will need to log out and log back in for this change to take effect. |
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:
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.
Step 1 |
Click the Settings icon and choose My Preferences. |
Step 2 |
Change the setting in the Items Per List Page drop down. |
Step 3 |
Click Save. |
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.
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 10 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
Step 1 |
Choose , then choose . |
Step 2 |
In the Global Idle Timeout area, make sure the Logout all idle users check box is selected (this means the mechanism is enabled). |
Step 3 |
Configure the timeout by choosing a value from the Logout all idle users after drop-down list. |
Step 4 |
Click Save. You will need to log out and log back in for this change to take effect. |