Error Message with IdP "LoginContext key cookie was not present in request"

[Mike Flynn]

When the error was reported to me by a user at the school I assumed that the school's cert had changed and apprised Ryan about it.  Ryan said no change had occurred so I sent him a copy of the metadata I had for their IdP.  Ryan said the copy I had matched his production version.  Ryan sent me his current production metadata and I checked it as well and it matched.  I loaded the copy that Ryan sent to me to my production servers but still the issue persists...



On Saturday, January 4, 2014 3:25 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
 
On 1/4/14, 6:19 PM, "Patrick Rynhart" <P.Rynhart at massey.ac.nz> wrote:
>
>Could you please advise what I need to do at my end to "fix" this
>problem, preferably without breaking the other SPs that we're federated
>with (along with Tuakiri which is our NZ access federation).

I don't have anything else useful to tell you. You asked what the error
means, that's what it means (which is exactly what it said, so it isn't
trying to be mysterious). The signature stopped working. The only reason
for that to happen between two unchanged Shibboleth peers is the key or
the metadata.

That assumes there's nothing in the log at the SP pointing to a different
explanation, but I have no idea what else it could be.

What it is *not* is a certificate expiring, or anything else that is going
to be time-based.


-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140104/d42faae5/attachment.html