"LoginContext key cookie was not present in request" with particular SP

[Ian Rifkin]

Hi,


> Is the SP signing the AuthnRequest? If so, the Destination XML
> attribute is required.


I'm not sure how to determine if it's signed, but I imagine it is given the
error. Watching my IdP logs with SPs that work, I see that some say "SAML
message intended destination endpoint in message was empty, not required by
binding, skipping" while others tell me the "SAML message intended
destination endpoint matched recipient endpoint."


> Alternatively, then can stop signing the request, especially if you have
> trusted metadata for the SP.
>

Ah, that's a good point. I will mention that to the SP vendor.

That said, I wrote that wikipedia entry, and if it's wrong, I will fix it.
>

Hopefully Scot can chime in, but now that I read the up on the destination
attribute in the standards document I think it's not that the wikipedia
entry is wrong, but that it doesn't mention destination attribute is
required if it's signed. Or perhaps just note something like that the
example is an example request and not meant to be the standard for all
requests?

Thanks,
Ian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130630/825f1778/attachment.html