For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Elio_Diaz_21163's avatar
Elio_Diaz_21163
Icon for Nimbostratus rankNimbostratus
Dec 02, 2015

Authentication behind F5 LineRate issue.

Hello everyone,   We are testing F5 Linerate as a LB solution for 2 of our core applications and found when we authenticate on the application directly the AD users are able to login without probl...
linerate
security
Johnny_Schmidt_'s avatar
Johnny_Schmidt_
Historic F5 Account
Dec 02, 2015
It is possible you are running in to an issue with NTLM authentication over HTTP (see http://www.innovation.ch/personal/ronald/ntlm.html for a good write-up on the subject). If this is the case, and your authentication mechanism is using NTLM over HTTP (which the default for some Microsoft web technologies) then you may have some challenges avoiding the re-authentication steps whenever the real-server connection is closed. As Andrew mentioned, persistence is necessary to make NTLM over HTTP work correctly, but preventing the connection from closing on the real-server side is the key to avoiding constant re-connection attempts. So double-check what the "WWW-Authenticate" header in the initial response looks like (using Chrome developer tools or similar) and if it is indeed of type NTLM then we can discuss how one might work around this with LineRate. Cheers, -johnny