Decoding encrypted attributes from an IDP

[Cantor, Scott]

> None of these errors showed up anywhere when the partner was just
> encrypting the attributes.  This set of errors showed up once I asked them to
> encrypt the assertion.  They indicated that they are encrypting both now
> (meaning, encrypt attributes, then encrypt the assertion), which seems
> pretty stupid so I hope that is not actually what they are doing.  Putting
> extractKeyNames=false into our config didn't actually solve the problem:

It's extractNames, actually, my mistake. And yes, if they don't stop encrypting twice, you'll be back where you started.

> Something must be wrong with either the public key we gave them or how
> they are using it, is all I can think.  Also, I have no idea how AES is coming into
> play since neither side is specifying to use AES anywhere.  Is that the default
> private key algorithm Shib uses?

Just ignore it, or you can read XML Encryption in your spare time if you want to know how it all works.

-- Scott