flowExecutionKey

Nate Klingenstein ndk at internet2.edu
Wed Jul 2 20:05:34 EDT 2014


I have updated the script to use brand new httpcore/httpclient 4.3.x libraries and 2.15 of htmlunit.

The script reused the same htmlunit WebRequestSetting object, which was replaced by WebRequest.  As part of the API change(I believe), it didn't unset the request parameter SAMLRequest.  There was no obvious way to unset the parameter, so I made a new WebRequest element for the SSO call.

This has been hard for me to debug because I can't find an immediate way to dump the actual HTTP objects.

I'm no longer getting any spurious results but I'm not able to proceed through the flows(or blow anything up) no matter what I change the query string to.  I think that bolster's Scott's original hypothesis about a munged POST query string.

If I forcibly set a _flowExecutionKey of e1s1(taken from the returned form) but leave the query string, nothing happens.  But if I ever remove the query string, I get:

23:32:52.367 - ERROR [org.opensaml.saml.saml2.binding.decoding.impl.HTTPPostDecoder:91] - Request did not contain either a SAMLRequest or SAMLResponse paramter.  Invalid request for SAML 2 HTTP POST binding.
23:32:52.373 - ERROR [org.opensaml.profile.action.impl.DecodeMessage:73] - Profile Action DecodeMessage: Unable to decode incoming request
org.opensaml.messaging.decoder.MessageDecodingException: No SAML message present in request

no matter what the _flowExecutionKey is set as, or whether it's set at all.

Grinder appears to be actively maintained, so I guess I'll try upgrading that next.  If that fails, then I'll start with whatever Marvin can supply.

Thank you for your patience as I learn and debug at the same time.


More information about the dev mailing list