Stress Testing Using NTLM Authentication
Look for an open source web testing tool that can do Windows authentication.
I've used openSTA and Pylot in very small amounts, but haven't found myself doing anything. openSTA says you can do NTLM here: http://www.opensta.org/docs/sclref/build-auth-blob.htm
I couldn't get it to work - possibly due to some network configuration or maybe my own mistake.
source to share
It would be a shame to restrict your testing tool because of the authentication issue. It is more practical to disable NTLM / Windows Auth during stress testing. We did this by adding a configuration parameter that only allows the username to be passed to the URL when configured in a load / load testing environment. This only changes behavior in one place, where we load and cache the current user. And it works with just about any testing tool.
If you are testing an ASP.NET application, you need to create your own user and assign it to HttpContext.Current.User. A good place to do this is in the AuthenticateRequest event for the HttpModule or membership provider, which you only configure in a stress test environment.
There are not many disadvantages to this technique. This works on the assumption that Windows Authentication is relatively cheap and relatively small compared to the performance of the generic application. We had high confidence in our stress test results without this. One caveat here is that IE will do the challenge / response with NTLM, so while this is not a perfect test, it is a very good test. And the perfect is the enemy of good.
source to share
You can try the Grinder project: NTLM support is a bit tricky, but there are some details here:
http://grinder.sourceforge.net/faq.html#spnego (embed link is now dead - see comment from CruiZen)
or
source to share