Santuario change

[Cantor, Scott]

We have a regression because of the bump of Santuario causing a failure on some encryption operations. It's possible it's my bug in the EncryptXXX actions, but Brent would have to weigh in on that.

The stack trace is:

2015-11-04 20:51:08,543 - ERROR [org.opensaml.xmlsec.encryption.support.Encrypter:542] - Error encrypting XMLObject
org.apache.xml.security.encryption.XMLEncryptionException: The element can't be serialized as it has no parent
	at org.apache.xml.security.encryption.XMLCipher.encryptData(XMLCipher.java:1146)
2015-11-04 20:51:08,550 - WARN [org.opensaml.saml.saml2.profile.impl.EncryptNameIDs:179] - Profile Action EncryptNameIDs: Error encrypting NameID
org.opensaml.xmlsec.encryption.support.EncryptionException: Error encrypting XMLObject
	at org.opensaml.xmlsec.encryption.support.Encrypter.encryptElement(Encrypter.java:543)
Caused by: org.apache.xml.security.encryption.XMLEncryptionException: The element can't be serialized as it has no parent
	at org.apache.xml.security.encryption.XMLCipher.encryptData(XMLCipher.java:1146)

The change to Santuario that's causing it is here:


http://svn.apache.org/viewvc/santuario/xml-security-java/tags/xmlsec-2.0.5/src/main/java/org/apache/xml/security/encryption/XMLCipher.java?r1=1683494&r2=1683510

It seems like a new restriction on the DOM we're encrypting. I'm seeing this encrypting NameIDs in a logout request because I haven't marshalled that message yet. I think assertion encryption is working in my testing because I signed it first, I'm going to check that assumption now.

-- Scott