unwrapped data has expired

[Cantor, Scott]

On 1/20/16, 12:28 PM, "users on behalf of Doan, Tommy" <users-bounces at shibboleth.net on behalf of tdoan at smu.edu> wrote:



>I’m finding a fairly high occurrence of this informational event recently logged in our IdP v3.1.2, however I’m not finding much help on it by searching around. Does this indicate a problem with sealer.jks?

It's most likely just users coming back after their session has expired (or in theory other pieces of data that are encoded, but sessions are the most frequent that time out like that). I left that on INFO mostly out of habit, it was INFO in the code I cloned it from, but it's probably not worth calling out in most cases.

> 
>Only in case it’s possibly related, I’ve had multiple users complain that they are seeing the Stale Request message in their browser even under normal SP-initiated user behavior immediately after authentication.

Nothing to do with that message.

> I actually experienced this
> myself this morning using a fresh browser session. I authenticated twice successfully, and was immediately presented with the Stale Request page both times.

Load balancing without sticky sessions is the usual cause if it doesn't involve a timeout or the back button. If you want to know why, check the log and correlate it to your address.

-- Scott