That did the trick Dan.Thanks a lot for the quick turn around.As we are planning to use the cxf 2.2.2 for our release,just wanted to know if this version of wss4j will be included with cxf 2.2.2.If it's a different version can you let us know which one will that be.
-----Original Message----- From: Daniel Kulp [mailto:[email protected]] Sent: Thursday, June 11, 2009 5:09 PM To: [email protected] Cc: bharath thippireddy Subject: Re: WS-Security RSA Excrytion exception.. Shoot. Yep. The code in the latest snaps did take on a direct dependency to BC. I just fixed that and a new SNAPSHOT is uploading now. Can you try again? Dan On Thu June 11 2009 3:50:48 pm bharath thippireddy wrote: > Dan, > > I see the following exception once I replace the wss4j jar as mentioned > below. > > java.lang.NoClassDefFoundError: org/bouncycastle/asn1/x509/X509Name > > org.apache.ws.security.components.crypto.CryptoBase.getAliasForX509Cert(Cr >yptoBase.java:302) > org.apache.ws.security.components.crypto.CryptoBase.getAliasForX509Cert(Cry >ptoBase.java:272) > org.apache.ws.security.message.token.SecurityTokenReference.getX509IssuerSe >rialAlias(SecurityTokenReference.java:560) > org.apache.ws.security.processor.EncryptedKeyProcessor.handleEncryptedKey(E >ncryptedKeyProcessor.java:202) > org.apache.ws.security.processor.EncryptedKeyProcessor.handleEncryptedKey(E >ncryptedKeyProcessor.java:107) > org.apache.ws.security.processor.EncryptedKeyProcessor.handleToken(Encrypte >dKeyProcessor.java:87) > org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEng >ine.java:326) > org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEng >ine.java:243) > org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInIn >terceptor.java:179) > org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInIn >terceptor.java:77) > > Is wss4j using bouncycastle classes ? > > Thanks, > Bharath > > -----Original Message----- > From: Daniel Kulp [mailto:[email protected]] > Sent: Thursday, June 11, 2009 3:33 PM > To: [email protected] > Cc: bharath thippireddy > Subject: Re: WS-Security RSA Excrytion exception.. > > On Thu June 11 2009 3:22:00 pm bharath thippireddy wrote: > > Dan , Can you please let me know how to pull in this fix? > > Just replace your wss4j jar with the latest snapshot from: > > http://people.apache.org/repo/m2-snapshot- > repository/org/apache/ws/security/wss4j/1.5.8-SNAPSHOT/ > > That should do it. > > Dan > > > Thanks and regards, > > Bharath > > > > -----Original Message----- > > From: Daniel Kulp [mailto:[email protected]] > > Sent: Thursday, June 11, 2009 1:19 PM > > To: Werner Dittmann > > Cc: [email protected]; [email protected]; bharath thippireddy > > Subject: Re: WS-Security RSA Excrytion exception.. > > > > On Thu June 11 2009 12:56:20 pm Daniel Kulp wrote: > > > On Thu June 11 2009 7:31:19 am Daniel Kulp wrote: > > > > On Thu June 11 2009 7:08:31 am Werner Dittmann wrote: > > > > > Daniel Kulp schrieb: > > > > > > Thus, for those URI's, xmlsec always uses the provider in the JDK. > > > IMO, WSS4J should match this, preferably by just calling into JCEMapper > > > so it always will use the same mapping. > > > > > > If there are no objections, I'll change the code to do just that. > > > > Just discovered Colm had already done this for trunk. Thus, just needed > > to be pulled back to 1.5.x branch. > > > > -- > > Daniel Kulp > > [email protected] > > http://www.dankulp.com/blog > > -- > Daniel Kulp > [email protected] > http://www.dankulp.com/blog -- Daniel Kulp [email protected] http://www.dankulp.com/blog
