You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Giuseppe Milicia <g_...@yahoo.it> on 2004/09/21 21:40:30 UTC

Problem with Signatures: Unexpected number of X509Data: for Signature

Hi guys,

I'm trying to use the WSS4J handlers to sign messages
from client to web service.

I think I configured everything all right, however I
get an exception at the client (way before sending the
SOAP request):

INFO: Using Crypto Engine
[org.apache.ws.security.components.crypto.Merlin]
AxisFault
 faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
 faultSubcode:
 faultString: WSDoAllSender: Signature: error during
message procesingorg.apache
.ws.security.WSSecurityException: General security
error (Unexpected number of X
509Data: for Signature)
 faultActor:
 faultNode:
 faultDetail:
       
{http://xml.apache.org/axis/}stackTrace:WSDoAllSender:
Signature: error
during message
procesingorg.apache.ws.security.WSSecurityException:
General secu
rity error (Unexpected number of X509Data: for
Signature)
        at
org.apache.ws.axis.security.WSDoAllSender.performSIGNAction(WSDoAllSe
nder.java:364)
        at
org.apache.ws.axis.security.WSDoAllSender.invoke(WSDoAllSender.java:2
81)
        at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
        at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
        at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
        at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:128)
        at
org.apache.axis.client.Call.invokeEngine(Call.java:2735)


For completeness my configuration is Axis 1.2 beta3,
WSS4J from CVS, Tomcat 5.0.28, java 1.4.0-b92 on
Windows XP

My handler are configured adding to the service the
request flow:
    <requestFlow>
        <handler
type="java:org.apache.ws.axis.security.WSDoAllReceiver"
>
           <parameter name="action"
value="Signature"/>
           <parameter name="signaturePropFile"
value="mycrypto.properties" />
        </handler>
    </requestFlow>

And similar at the client. I do have the Axis generate
client-config.wsdd in the classpath.

My keystore is JKS with the appropriate keys, however
I get the same problem with the standard WSS4J
crypto.properties and associated keystore.

Any ideas or clues would be very much appreciated!

-- Giuseppe





		
___________________________________
Scopri Mister Yahoo! - il fantatorneo sul calcio di Yahoo! Sport
http://it.seriea.fantasysports.yahoo.com/