SP question -- saving POST data

[Cantor, Scott]

On 10/16/13 7:41 PM, "Steven Carmody" <steven_carmody at brown.edu> wrote:

>On 10/16/13 6:31 PM, Cantor, Scott wrote:
>> On 10/16/13 5:21 PM, "Steven Carmody"<steven_carmody at brown.edu>  wrote:
>>>
>>> What should I be looking for in the log files ?
>>
>> There won't be anything unless something failed. That's all the expected
>> output. The delete happens after it successfully reads the data back.
>>
>
>Sorry - should have been clearer. It reads the data back, and then stops
>here:
>
>https://www.brown.edu/Shibboleth.sso/SAML2/POST#submitted

I don't know what that #submitted thing is, that's not my code. That
doesn't exactly scream "correct" to me.

Maybe you have a cookie problem. The SP has to use a cookie for this
because it's already using RelayState to carry information about the
resource. The actual data is stored in the StorageService, but the storage
key is put into a cookie, like the original RelayState handling was.

But that doesn't fit your log. The delete of the record means it recovered
the cookie and there simply isn't any way for it to break after that other
than for the template being returned to break. I have nothing I can
suggest.

>If there's already a Shib session at the SP, it works OK.

If there were a session, this feature wouldn't be involved.

-- Scott