Reputation: 2539
I am testing an application that requires a user to authenticate, and then uses a cookie to track the user session. If authentication fails, a cookie is set that identifies the session as belonging to an unidentified user.
Unfortunately, authentication is via Kerberos or NTLM, which cannot be done in JMeter 2.8. My plan is therefore as follows:
Essentially, this is session hijacking.
What I am observing is that (1) the JMeter cookie manager does not seem to be supplying the cookie to the application in the first request, (2) after the first request the application sends a different cookie back to JMeter, and (3) subsequent requests use the application-defined cookie, not the one I supplied.
So my questions are:
Thanks in advance.
Upvotes: 0
Views: 1034
Reputation: 34536
Try using JMeter nightly build, it has been reported recently that it worked with NTLM after upgrade of httpclient libraries.
You approach seems really weird to me and I don't think it will work or even if it does be realistic.
Upvotes: 1