Forum Discussion
F5 seems to break NTLM Auth when using Powershell but ok with browser
I've done some capture and I can see that Powershell via direct call use Kerberos authentification
A browser use NTLM authentification always (direct call or via F5)
So why Kerberos isn't working with F5 in front and powershell ?
The first response from the backend server is always like this (with F5 or not) : HTTP/1.1 401 Unauthorized Content-Length: 0 Server: Microsoft-HTTPAPI/2.0 WWW-Authenticate: Kerberos WWW-Authenticate: NTLM WWW-Authenticate: Basic
When direct call, powershell send a Kerberos token in the next request and it works When F5 is in front, Powershell doesn't send a next request
A browser send a NTLM token in the next request, with F5 or direct call
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
