SP datasealer and XSECCRYPTOEXCEPTION

[Cantor, Scott]

> terminate called after throwing an instance of 'XSECCryptoException'

It's a bug, I never remember that XSECCryptoException isn't a subclass of XSECException in that godforsaken library and the code is only catching the latter right now.

> I'm hoping for thoughts on further troubleshooting the source of this. Could it be that our data sealer key file doesn't
> contain the latest key from the other node that generated the encrypted cookie? I think they're in sync, but it's the
> only explanation I've come up with. Would failure to decrypt with any keys result in this exception?

Without catching it and getting the exception message out I couldn't say what the underlying error is, just that the decrypt is throwing.

-- Scott