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

[Nate Klingenstein]

Your metadata should be fine and they are likely not selecting the binding that they think they're selecting.

You may consider showing them the full incoming message as useful debugging information, which will be accessible either by browser trace or by turning on DEBUG logging for the root level and protocols messages in logging.xml.

On Jun 27, 2013, at 20:44 , Ian Rifkin wrote:

> I wrote to this SP vendor again and they claim "We are using SAML 2.0 with the HTTP-Redirect protocol. The metadata file indicates the /idp/profile/SAML2/Redirect/SSO as the endpoint."
> 
> I think they are referring to the location attribute on the SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" element in my metadata file.
> 
> Is there something wrong in my metadata file? Is the SP vendor reading the metadata document incorrectly? Other?