Answer the question
In order to leave comments, you need to log in
Has anyone been able to set fiddler to transparent kerberos or ntlm authentication?
Few details.
I have a corporate proxy with ntlm or kerberos authentication at work. Authenticates through a corporate account. fiddler has a setting in the menu:
The documentation says that "should work", i.e. transparently authenticate. Does not work. It is also recommended to set it up like this:
The result is the same - the application returns 407 an authentication request. Is this generally possible with fiddler2? What could be the problem (maybe in a corporate proxy, but I don’t know how to prove it)?
Answer the question
In order to leave comments, you need to log in
Not even a couple of months passed, as it turned out what was the matter. There is such a stream button:
If it is enabled, then fiddler does not affect the data that it passes through itself in any way. Only shows them. But if it is turned off, then you can already modify the data, for example, change the cookie, add a header to the package, and, finally, this damn pass-through authentication will work. But there is also a moment. It depends on what kind of authentication this is. The ntlm authentication in the domain worked, but the authentication on the internal proxy did not work for some reason. But these are subtleties. The main thing is to find the root of the problem.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question