Last Modified: Apr 17, 2024
Affected Product(s):
BIG-IP APM
Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4
Opened: Oct 27, 2020 Severity: 3-Major
POST requests to an IdP resource URI /saml/idp/res?id=<idp_resource> results in APM not responding (the issue also occurs with URI /saml/idp/res). The issue occurs when there is no Access session established yet. After an Access session is established, POST requests complete without issue.
POST requests to the URI /saml/idp/res... result in user-agent hanging and the request never completes
-- APM IdP Resource -- POST request to the URI /saml/idp/res... prior to Access session established
-- Refresh the request on the user-agent -- Configure environment to have user-agent do GET request method -- iRule that redirects user-agent from POST method to GET method. For EXAMPLE: when CLIENT_ACCEPTED { ACCESS::restrict_irule_events disable } when HTTP_REQUEST { if { [HTTP::uri] contains "/saml/idp/res" && [HTTP::method] eq "POST" } { if { [ACCESS::policy result] eq "" or [ACCESS::policy result] eq "not_started" } { HTTP::respond 302 "Location" "https://[HTTP::host][HTTP::uri]" "Connection" "Close" } } }
None