HI Chankami, In this cases these IDPs will identify these request as an attack and block. And I don't think its useful to load the IDP. I think your objective is to check whether IS can handle federation flow.
In that case you can use another IS as a IDP and do the test. -Ishara On Wed, Nov 29, 2017 at 3:03 PM, Chankami Maddumage <[email protected]> wrote: > Hi All > > We have a solution to automate Google federated authenticator as IDP > where travelocity is used as SP. > > I have used Jmeter to automate this scenario. When I access my SP, > travelocity, it redirects to the Federated IDP Google Login page. Ideally > if I login via Google login page, it redirects me to the tavelocity logged > in page. > > When I capture the request, I can see multiple parameters which are > auto-generated from Google side is passed for the login request. > > Also, When we try to load test Google side, they block our requests. > > My question is, since I am in a process to Stress test WSO2 IS federated > authenticator login scenario, please advice me up to which level I should > do the stress testing? > > > Example, should I stress test only up to the login page or is there any > other correct way to proceed with this scenario. > > > This problem is there for other connectors like Facebook, twitter etc > > -- > Best Regards, > > > *Chankami Maddumage* > Software Engineer - QA Team > WSO2 Inc; http://www.wso2.com/. > Mobile: +94 (0) 722223096 <%2B94%20%280%29%20773%20381%20250> > > -- Ishara Karunarathna Technical Lead WSO2 Inc. - lean . enterprise . middleware | wso2.com email: [email protected], blog: isharaaruna.blogspot.com, mobile: +94717996791
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
