algorithm URI was invalid: http://www.w3.org/2001/04/xmlenc#aes128-cbc

[Joy Veronneau]

Hi,

I am still having trouble tracking down what is causing this issue. I've redone the installation and double checked all the files (including the war file and deployment). I've restarted with Java 1.6. The only way to fix it is to set up the troublesome providers for encryptAssertions="never".

Our setup is:
IDP 2.4
Java 1.7
Tomcat 6.0.20 (endorsed libraries updated)
Apache 2.2.20
Redhat 5.9

I would appreciate any other ideas!

Thanks,

Joy

On Sep 22, 2013, at 3:06 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

> On 9/22/13 2:04 PM, "Joy Veronneau" <jv11 at cornell.edu> wrote:
> 
>> Thanks, I will check. It seems to be happening only with IIS 7  sp
>> servers - does that suggest anything else?
> 
> There is no possible way this can be confined to any specific SP,
> implementation, web server, or anything else not running on the IdP
> machine.
> 
> I can't think of any other cause but a corrupt installation. Maybe a stale
> Tomcat working copy or something like that.
> 
> -- Scott
> 
Hi, 

This morning I upgraded our Shibboleth IDP from version 2.3.3 to version 2.4. I am seeing quite a few of these errors (below). 

Any ideas what might be causing this and how to fix it?

Thanks!

Joy

13:24:03.463 - ERROR [org.opensaml.xml.encryption.Encrypter:649] - Could not generate encryption key, algorithm URI was invalid: http://www.w3.org/2001/04/xmlenc#aes128-cbc
13:24:03.467 - ERROR [edu.internet2.middleware.shibboleth.idp.profile.saml2.AbstractSAML2ProfileHandler:294] - Unable to encrypt assertion
org.opensaml.xml.encryption.EncryptionException: Could not generate encryption key, algorithm URI was invalid: http://www.w3.org/2001/04/xmlenc#aes128-cbc