Highlighted
Absent Member.
Absent Member.
10095 views

Loadrunner problem with single sign on

Hi All,

I am currently suing loadrunner 9.1.
I am facing some problem with single sign on and loadrunner.
I ran a test yesterday with 25 users and 25 userid's. I used the
web_set_user to set all the users. But I see a strange behavior.

Though the loadrunner logs show that each virtual user is using unique
id's , But when I told the admin to check the webseal logs for that
particular test duration it showed only two Id's that are logged on.The
transactions are also getting lodged on mainframes under two id's although
25 unique id's have been used.

Do I need to make any configuration changes so that all user id's are
visible on the webseal logs?
All the 25 user Id's are valid id's in that particular domain and also have
access to mainframes to lodge the transaction.

And I have used the function web_set_user
("{DomainName}\\{UserName}","{Password}","uatinternal.corp.aal.au:443");

Currently I have test users : TRNIT1-TRNIT25 and mine for 1 script
and : BATPT55-BATPT100 for
another script

So even though load runner logs show that each virtual user is using
different Id, but in the webseal its showing two users (one mine and
TRNIT01) and (BATPT55 and BATT56).
Although the loadrunner logs show that virtual user TRNIT24 is logged in
and making the transaction but in the mainframes its lodged under either
mine or TRNIT01.
I have checked that all the transactions from all the users are valid and
getting logged.
Also I have enabled the following :

1. Winlet replay instead of sockets.
2. Enable integrated authentication
3. Use Windows native NTLM authentication
4. Override credentials in Windows native NTLM authentication


Could someone explain this behavior of loadrunner with single sign on?
0 Likes
7 Replies
Highlighted
Absent Member.
Absent Member.

Re: Loadrunner problem with single sign on

I believe that if you have set "WinInet replay instead of sockets.", web_set_user will not matter. I am not sure but I think you can try to uncheck that option.

Secondly, check for missing correlations. It may happen that the script is passing but the sessions are not getting closed completely in the script. In this case, you need to make sure all correlations are taken care of.

Also, you can try by checking the Simulate new user & clear cache on each iteration options in RunTime Settings (I am assuming that you have your entire code in the action section)
0 Likes
Highlighted
Established Member..
Established Member..

Re: Loadrunner problem with single sign on

just one work around....try manually to log in to the system with 4 or 5 or 6 different users from different machine and then during that period check the logs.....now after analysing that tell us what happend.....i think from this u can find out the problem.....also let us know what is the result.

Thanks,
Prasenjit
Highlighted
Absent Member.
Absent Member.

Re: Loadrunner problem with single sign on

Hi,
I did two things:
1. Correlated the cookie: web_add_cookie("LFR_SESSION_STATE_24501=1306193366994;
DOMAIN=uatinternal.corp.aal.au");
2. Run vuser as a process

And it worked.

If I use run vuser as a thread, it does not work.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Loadrunner problem with single sign on

You can delete all the cookies in your script.They are not required during replay of your script.
0 Likes
Highlighted
Frequent Contributor.
Frequent Contributor.

Re: Loadrunner problem with single sign on

Web Seal does not allow you to log in multiple users with the same ip address.  To prove this try logging into the application two users on different tabs.  This test can only be done using ip spoofing. I am having the same problem and will implement ip spoofing. When I log in two users from the same machine the other one gets ignored and I automatically have a repeat of the first session i started.

0 Likes
Highlighted
New Member.

Re: Loadrunner problem with single sign on

Hello All, 

Small question, do you face issue using LoadRunner 12.53  with SSO using web html/http protocol, also 

I guess truclient protocal can be used as well but afraid of handling SSO credential.

 

 

0 Likes
Highlighted
Respected Contributor.
Respected Contributor.

Re: Loadrunner problem with single sign on

Hi Tanisha,

For Single Sign on we need to use tha appriate mappings and filter first.

Need to add correct port mapping entries in Mapping and Filtering section

Record >> Recording Options >> Network >> Mapping and Filtering -> Use both Socket and Wininet level option

  1. Record the business process
  2. Ensure the all the required web_set_sockets_options are added to the script
    1. web_set_sockets_option("SSL_VERSION", "TLS"); - for WinSSO related scripts
    2. web_set_sockets_option("SSL_VERSION", "TLS1.2"); for  actual application related steps
  3. Final step, based on the Fiddler and IE developer tools, need to change one of the step location (first step in the script needs to move after the WinSSO related steps).

        This step might be applicable for this application but tester needs to verify in order to resolve the issue.

Replay the script with extended log option and validate the results.

 

Thank you.

 

 

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.