Bug ID 438958: maximum session timeout of 0 is not infinite

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.6.0

Opened: Nov 25, 2013
Severity: 3-Major
Related AskF5 Article:
K15146

Symptoms

If an administrator sets the Maximum Session Timeout to 0 (zero), APM interprets it as exactly 7 days instead of interpreting it as infinite as expected.

Impact

Affects all versions after 11.0.0.

Conditions

Set the Maximum Session Timeout to 0.

Workaround

Put a really large value for the session timeout. For example, 999999999 is an allowed value, which will be about 31 years and 8 months, effectively "infinite".

Fix Information

None

Behavior Change