Previously I identified a way in which to test SPNEGO or Kerberos authentication with LoadRunner. However this implementation was buggy in the sense that if you ran your load tests under reasonable load with the WinInet replay engine (instead of sockets) you were likely to encounter the following error:
Error -27492: "HttpSendRequest" failed, Windows error code=12057 (certificate revoked) and retry limit (0) exceeded for URL="
https://someplacesecure.com.au/secure.html", Snapshot Info [MSH 1 2]
This error occurs when using WinInet replay instead of sockets with Integrated Authentication enabled in run-time settings. The purpose of this was to allow vusers to use SSO with SPNEGO authentication in an IBM WebSEAL environment.
After spending some time with the mystical HP level 3 support, they identified an undocumented flag which helps out significantly in this. So, instead of using the WinInet replay engine (which is not encouraged by HP) you should do something similar to the following.
vuser_init() { // Preferred run-time settings // Browser -> Browser Emulation // [ ] Simulate a new user on each iteration // Preferences -> Options // Enable Integration Authentication [Yes] web_set_sockets_option("INITIAL_BASIC_AUTH","1"); web_set_user("DOMAIN.LOCAL\\username", "password", "someplacesecure.com.au:443"); web_url("myportal", "URL=https://someplacesecure.com.au/wps", "Resource=0", "Referer=", "Mode=HTML", LAST); return 0; }
The magic is in the web_set_sockets_option("INITIAL_BASIC_AUTH","1") flag. Set that and you can then use LoadRunner in Sockets mode which as it turns out, is much more stable.
Enjoy.
Read More