Hello, I am trying also but having some difficulties with The keygeneration for the .net side.
I used keytool to generate the keys. Then I converted the keys from keytool in pfx format. I succeeded to install those keys in windows keystore. Fernando may you tell me how are generated the key for Alice and Bob to pfx format? In which format are stored the key in the javakey store, JKS format? Freeddy, May you show me your wssd deployment in the java server side? Thank you in advance to you both. On 3/25/07, Ruchith Fernando <[EMAIL PROTECTED]> wrote:
Hi, Can you please post the message that the java service gets from the .NET client? Thanks, Ruchith On 3/23/07, Freddy Weishaeupl <[EMAIL PROTECTED]> wrote: > Hi, > > currently I'm trying to use a .NET Client to access a Java webservice. At > the .NET side I use the Microsoft WSE 3.0 implementation to sign and encrypt > the SOAP Body of the SOAP request message. At server-side WSS4J is used for > checking the signature and decrypting the SOAP Message. > > I'm using the interop certificates (Alice&Bob) of the WSS4J 1.5.1package. > > Unfortunately at server-side I always get the following error message: > ----------------------------------------------------------------------------------------------------------------- > ... > [23.03.2007 14:53:37] [DEBUG] > [org.apache.xml.security.algorithms.SignatureAlgorithm.<init>] Create URI > "http://www.w3.org/2000/09/xmldsig#hmac-sha1"; class "class > org.apache.xml.security.algorithms.implementations.IntegrityHmac$Integrity > HmacSHA1" > [23.03.2007 14:53:37] [DEBUG] > [org.apache.xml.security.algorithms.JCEMapper.translateURItoJCEID] Request > for URI http://www.w3.org/2000/09/xmldsig#hmac-sha1 > [23.03.2007 14:53:37] [DEBUG] > [org.apache.xml.security.algorithms.implementations.IntegrityHmac .<init>] > Created IntegrityHmacSHA1 using HmacSHA1 > [23.03.2007 14:53:37] [DEBUG] > [org.apache.xml.security.utils.ElementProxy.<init>] setElement("KeyInfo", > "null") > [23.03.2007 14:53:37] [DEBUG] > [ org.apache.ws.security.message.token.SecurityTokenReference.getTokenElement ] > Token reference uri: #SecurityToken-d81c5ccf-8197-433f-937b-495421e6a832 > org.apache.ws.security.WSSecurityException: Referenced security token could > not be retrieved. (Reference > "#SecurityToken-d81c5ccf-8197-433f-937b-495421e6a832") > at > org.apache.ws.security.message.token.SecurityTokenReference.getTokenElement (SecurityTokenReference.java:179) > at > org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature( SignatureProcessor.java:186) > ... > ----------------------------------------------------------------------------------------------------------------------------------------- > > > Any ideas what's the problem here? Has anyone already tested WSE3.0 in > combination with WSS4J? > > Thanks. > > Best Regards > Freddy > > _________________________________________________________________ > Express yourself instantly with MSN Messenger! Download today it's FREE! > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- www.ruchith.org www.wso2.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- José Ferreiro EPFL Communication Systems engineer ing.sys.com.dipl.EPFL
