Bug ID 528416: Include Basic auth challenge in 401 F5 Authorization Required response

Last Modified: Apr 10, 2019

Bug Tracker

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

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, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0

Opened: Jun 17, 2015
Severity: 3-Major

Symptoms

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.

Impact

Because of the missing Basic Auth challenge, browser/soapUI/Postman tools cannot use cached user credentials.

Conditions

Issue happens with cookie (BIG-IPAuthCookie) based authentication.

Workaround

Workaround is to remove the cookie (BIG-IPAuthCookie) from browser session so it does not get included in the sent request.

Fix Information

This release now includes a Basic Auth challenge (WWW-Authenticate header) in 401 F5 Authorization Required responses.

Behavior Change