Turns out my earlier 'solution' was a red herring.
So I'm still stuck with the problem that I can't get CAS to handle this particular IDP which send encrypted responses. I've confirmed that the cert that they are using matches the one in the metadata etc.
I'm assuming that if there was a mismatch in times, then that would show up as a skew error rather than a failure to decrypt the message? I'm also assuming that since CAS is trying to decode it, it at least knows it is encrypted - is it possible that the key is not where it's expecting it (and is that a CAS issue for not looking or a provider one for being 'different') - obviously this is a bit of a stretch suggestion as I don't know if it would even be possible to return it in different places within the response!
Thanks
Chris
On Friday, 31 March 2023 at 23:34:19 UTC-5 Chris Durham wrote: