Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
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, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 11.6.4
Opened: Jun 17, 2015
Cookie (BIG-IPAuthCookie) based authentication is no longer supported for iControl REST API to prevent CSRF security vulnerability. But when a logon fails the authentication, there is no basic auth challenge (WWW-Authenticate header) in the response.
Because of the missing Basic Auth challenge, browser/soapUI/Postman tools cannot use cached user credentials.
Issue happens with cookie (BIG-IPAuthCookie) based authentication.
Workaround is to remove the cookie (BIG-IPAuthCookie) from browser session so it does not get included in the sent request.
This release now includes a Basic Auth challenge (WWW-Authenticate header) in 401 F5 Authorization Required responses.