Forum Discussion
Check the Request 2 headers in the logs - there is no "NID=71=Nj...." cookie simulated. And Request 1 does not set that cookie anywhere, hence it's not simulated. The cookie is set in Request 3 of the recorded scenario, but this request is disabled.
So, looks like this SSO scenario was too tricky for LoadComplete to record the right sequence of requests, a couple of requests were mixed up. I think you need to re-enable Request 3 in the scenario, switch to the Connection view, and Move Up "Request 3" to change the recorded request order. You will also need to correlate the re-enabled Request, it has some dynamic parameters.
Let me know if you need help with this! I can't run your scenario, but I can try to make some changes on my side and send it to you in a response to your case so you can check how it works.
It's really taking me too much time so i switched to used office365 signin instead of Google to do some performance and load test for now but thanks for the feed back. i will try work on it after release.
- AlexanderM9 years agoStaff
Good to hear you have an alternative solution! Let me check with the LoadComplete Devs if this is something we can improve in the future - auto-correlating the SSO traffic that uses Google as a provider... When I have some news, I'll drop you a line!
- augustine_uzokw_19 years agoContributor
thank you :)
- AlexKaras9 years agoChampion Level 3
Alex,
Thank you a lot for all the information posted here.
> When I have some news, I'll drop you a line!
I will really appreciate if you copy the message to this thread as well.
Related Content
- 7 months agomengbinhao
Recent Discussions
- 6 months agowesMHu
- 2 years agoaa1
- 3 years agoSubu
- 3 years agojoegriffitts