Bug ID 495265: SAML IdP and SP configured in same access profile not supported

Last Modified: Aug 19, 2026

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 hf1, 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.1 hf10, 11.5.1 hf11, 11.5.2, 11.5.2 hf1, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0, 11.5.3

Opened: Dec 08, 2014

Severity: 3-Major

Symptoms

SLO might not work properly under certain conditions. When a user attempts to start SLO, the connection gets reset. The system logs messages such as the following: RST sent from x.x.x.x:433 to x.x.x.x:xxxx, [0xxxxxx:xxx] Internal error ((APM::SSO) Error in reading sp info from session db failed)

Impact

SLO is not properly executed; users's session might not be terminated.

Conditions

All conditions must be met: 1. Both BIG-IP as SP and BIG-IP as IdP are configured on the same access profile. 2. SLO is configured for both BIG-IP as IdP and BIG-IP as SP. 3. SLO is executed in multiple TCP sessions between the user's browser and the BIG-IP system.

Workaround

None.

Fix Information

A problem with SAML single-logout has been fixed.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips