OpenSAML user discussion

[Scott Cantor <>]

 This issue comes up every once in a while, so for those using OpenSAML with
WebSphere, I guess the problem is that it used IBM's JDK and it doesn't come
with Sun's JCE (obviously).

I guess that's why plugging in the Bouncy Castle JCE is a fix.

-- Scott

-----Original Message-----
From: Stephen Chell (DSL AK) 
[mailto:]
 
Sent: Monday, April 19, 2004 8:03 PM
To: 
''
Subject: RE: XMLSignatureException: The requested algorithm ... does not e
xist

After further investigation, the problem seems to be the combination of the
following two factors:
 
1.  the JCE Algorithm Mappings specified in
org/apache/xml/security/resource/config.xml do not include any mappings for
IBM
 
2.  the JDK and libraries supplied with Websphere do not include the
following class:  sun.security.provider.Sun
 
Any suggestions as to how to get around this problem?   
 
Thanks in advance ...
 
Steve
 
 

        -----Original Message-----
        From: Stephen Chell (DSL AK) 
        Sent: Monday, 19 April 2004 4:47 p.m.
        To: 

        Subject: XMLSignatureException: The requested algorithm ... does not
exist
        
        
        I'm getting the following exception in Websphere Application Server
5.1 (which uses JRE 1.4.1) when I attempt to instantiate an XMLSignature
object from a fragment of XML.  
         
        org.apache.xml.security.signature.XMLSignatureException: The
requested algorithm http://www.w3.org/2000/09/xmldsig#dsa-sha1 does not
exist. Original Message was: null
        Original Exception was java.lang.NullPointerException
         at
org.apache.xml.security.algorithms.SignatureAlgorithm.<init>(SignatureAlgori
thm.java:217)
         at
org.apache.xml.security.signature.SignedInfo.<init>(SignedInfo.java:213)
         at
org.apache.xml.security.signature.XMLSignature.<init>(XMLSignature.java:281)
         at
nz.govt.ssc.eai.common.message.EAIMessage.verifyMessageSignature(EAIMessage.
java:434)
         ... 24 more
         
         
        It works fine in Tomcat 4.1.29 using JDK 1.4.2_04, but in Websphere
I get the above exception.  My understanding was that the crypto algorithms
come built in to JDK 1.4 and above.  Is that correct?  If so shouldn't it
work with WebSphere, which uses 1.4.1?
         
        Thanks in advance ...
        Steve