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

[Patrick Rynhart]

On 5/01/2014 9:53 a.m., Cantor, Scott wrote:
> On 1/4/14, 3:56 AM, "Patrick Rynhart" <P.Rynhart-GuuZuZYZZ9vScTE++YW6Eg at public.gmane.org> wrote:
>>
>> Firstly, I thought that the "LoginContext key cookie" message was the
>> cause (and the message displayed in the UI a fallback / secondary error
>> message, i.e. not necessarily the "cause").
>
> That's incorrect.
>
>> To answer your question, the message displayed in the UI is:
>
> Which means you changed your signing key without updating your metadata
> and doing a controlled key rollover.

Not sure how this could have happened.  I was away on Christmas break 
from when things were working - and got an email saying that this 
problem had developed midway through.  I hadn't logged onto the box 
during this time, and I'm also the only admin of it.

>
>> This suggests that it's a metadata issue.  If so, the problem now is
>> that I haven't changed the metadata at my end (and I'm successfully
>> federated with other external SPs which are still working.)  I've also
>> been in touch with Lynda.com technical support who have said that my
>> metadata hasn't been changed at their end.
>
> Your key did change, or the error wouldn't have occurred. Or the metadata
> given to the SP did in fact change and no longer is correct.

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).

Thank you for your time.

Patrick Rynhart
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to users-unsubscribe-42IIvhcvNBnXOH51mAaJLw at public.gmane.org
>