Yeah, that "Unexpected number of X509Data: for Signature" error message is annoyingly nonsensical--I submitted a JIRA a couple months back to the WSS4J team for them to fix it. Did you see my blog entry on using x509? It's here: http://www.jroller.com/gmazza/entry/implementing_ws_security_with_the
If you can't get it working with CXF, Metro is another option, they do a lot of interoperability testing with .Net so you may have more success with them: http://www.jroller.com/gmazza/entry/implementing_ws_security_with_pki HTH, Glen CXF-de'per wrote: > > I have a restriction not to use trasport level SSL... instead I can use > the X509 certificate... where .Net service provides... > now the next question: If I use the x509 certificate... how do I use > that... I am getting the following error > I have key.cer... > I generated the xyz.jks... > > > Caused by: org.apache.ws.security.WSSecurityException: WSHandler: > Signature: error during message > procesingorg.apache.ws.security.WSSecurityException: General security > error (Unexpected number of X509Data: for Signature) > -- View this message in context: http://www.nabble.com/%3Centry-key%3D%22passwordType%22-value%3D%22PasswordDigest%22--%3E-follows-which-algorithm--to-encrypt-tp19416347p19426783.html Sent from the cxf-user mailing list archive at Nabble.com.
