It seems "Idle Session Timeout" doesn't work for HTTP/HTTPS connections on CBS250 series switches?
(example from a CBS250-24P-4X)
Updating value via web interface doesn't affect 'running-config', and user sessions get terminated after about 5 minutes regardless what the setting is set to (via web interface).
After setting HTTP/HTTPS session timeout to 30 minutes, and logging out and logging back in (and clicking "Port Management"), and leaving browser window 'idle':
23-Sep-2021 11:41:07 %AAA-I-CONNECT: New http connection for user admin, source 172.16.1.42 destination 172.16.1.10 ACCEPTED
23-Sep-2021 11:47:57 %AAA-I-DISCONNECT: http connection for user admin, source 172.16.1.42 destination 172.16.1.10 TERMINATED
switch1#sh ver
Active-image: flash://system/images/image_cbs250_ros_3.1.1.7_release_cisco_signed.bin
Version: 3.1.1.7
MD5 Digest: 4805a22186295e82609a0a3e6def88e0
Date: 12-Aug-2021
Time: 15:02:37
Inactive-image: flash://system/images/image_cbs250_ros_3.1.0.57_release_cisco_signed.bin
Version: 3.1.0.57
MD5 Digest: 9eac4c7725aaf03a8d8cfd1bf909edf3
Date: 18-Jan-2021
Time: 18:07:11
switch1#
Update:
Configuring timeout policy via CLI doesn't seem to have any effect either:
switch1#sh run | include ip http
ip http timeout-policy 0
switch1#
Still getting disconnected in about 5-10 minutes:
23-Sep-2021 12:27:11 %AAA-I-CONNECT: New http connection for user admin, source 172.16.1.42 destination 172.16.1.10 ACCEPTED
23-Sep-2021 12:34:58 %AAA-I-DISCONNECT: http connection for user admin, source 172.16.1.42 destination 172.16.1.10 TERMINATED
