SP datasealer and XSECCRYPTOEXCEPTION

[Wessel, Keith]

Thanks, Scott. Shall I file a bug, or do you want to take care of it I'm happy to, but you've probably noticed that most of the bugs I file get filed under the wrong categories. The dropdowns in Jira aren't too screen reader friendly. :)


Keith


-----Original Message-----
From: users <users-bounces at shibboleth.net> On Behalf Of Cantor, Scott
Sent: Tuesday, October 30, 2018 4:27 PM
To: Shib Users <users at shibboleth.net>
Subject: Re: SP datasealer and XSECCRYPTOEXCEPTION

> 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


--
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net