¡Hola!
> On 03 Mar 2016, at 00:53 AM, Francisco Almeida <
fral...@gmail.com> wrote:
> Hi Jaime,
>
> If I use the Browser (IE, Firefox, ...) everything works fine (my IdP is an ADFS Server). When I am trying to replicate the steps to JMETER is where the problem happens.
>
> One thing that I've doubts is related with the request to "adfs/ls" (HTTP POST) where I've seen the XML request
> -----------------
> <trust:RequestSecurityTokenResponseCollection xmlns:trust="
http://docs.oasis-open.org/ws-sx/ws-trust/200512">
> (...)
> </trust:RequestSecurityTokenResponse>
> ————————
That’s not SAML at all, so I can’t help you much with that :-(
> with white spaces or with "+" (in this case replacing the white spaces). Could this have anything to do with the error?
That’s due to base64 encoding, and it depends on the particular encoding used. In general, it shouldn’t be a problem, but it might be that the recipient of the base64-encoded string is expecting a different encoding.
> Do you recommend anything to automate tests with SSO workflow?
I’ve used jmeter myself many years ago, and it worked fine. However, it’s difficult to use, and you need to add a lot of logic. Or at least you needed, because jmeter would not follow redirections or keep cookies back in the day. I don’t know how it is coping with all that nowadays.
Another option that might be more interesting for you is selenium, which you can use to automate testing with real, headless web browsers. But of course that’s more intended to test behaviour rather than performance, so it depends on what you want exactly.