Hi,
I had he same problem when using wss4j on WebLogic 9.2.
I put it down to the fact that wss4j loads the BouncyCastleProvider JCE
provider at position 2. This was not causing a problem on old versions
of WebLogic but WebLogic 9.2 inserts its own JCE provider at position 1.
This causes all existing providers to shift down. When wss4j comes along
and inserts the BouncyCastleProvider at position 2 it is actually
inserting in front of the Sun provider. BouncyCastleProvider has a
dependency on the Sun provider and therefore can't be placed at a higher
position than Sun.
The only way I got it to work reliably was to change the WSSConfig class
within wss4j to insert at position 3.
We really need to find a way of making the provider position used by
wss4j configurable. The default should be 2 but WebLogic 9.2 needs
position 3 and if you are using WebLogic 9.2 on AIX you need position 4.
I have changed my version of WSSConfig getNewInstance() as follows:
public static WSSConfig getNewInstance() {
String configClass = System.getProperty("defaultwssconfig");
WSSConfig config;
if(configClass != null && configClass.trim().length() > 0 ){
try {
config = (WSSConfig)
Class.forName(configClass).newInstance();
} catch (InstantiationException e) {
config = new WSSConfig();
} catch (IllegalAccessException e) {
config = new WSSConfig();
} catch (ClassNotFoundException e) {
config = new WSSConfig();
}
}else {
config = new WSSConfig();
}
return config;
}
This allows the implementation of WSSConfig to be changed based upon a
system property. Is there any change of getting something similar in to
the official wss4j?
Hope that helps,
Regards,
Chris.
________________________________
From: wss4j wei [mailto:[EMAIL PROTECTED]
Sent: 28 August 2007 23:59
To: [email protected]
Subject: wss4j - weblogic 9 with An unsupported signature or encryption
algorithm was used (unsupported key transport encryption algorithm: No
such algorithm: http://www.w3.org/2001/04/xmlenc#rsa-1_5
Hi All,
Weblogic : An unsupported signature or encryption algorithm was used
(unsupported key transport encryption algorithm: No such algorithm:
http://www.w3.org/2001/04/xmlenc#rsa-1_5
I have written a new handler which extends from WSHandler and
implements Handler. Not sure it has anything to do with this. I suppose
it is not.
Not sure is it related to xml security[xmlsec-1.4.0.jar] loading in the
weblogic's webapp lib level.
If I copy the jar to the application's lib level, It works fine [able to
find key transport encryption algorithm such as #rsa-1_5].
If I copy the jar to the webapplication's lib level, it errors with An
unsupported signature or encryption algorithm was used (unsupported key
transport encryption algorithm: No such algorithm:
http://www.w3.org/2001/04/xmlenc#rsa-1_5
Anyone has this issue ? or any idea why I am getting this.
