Ron, at the receiver the order of elements during parsing and processing is not important.
According to the exception thrown it seems that you don't have a Signature crypto file specified in the WSDD (or otherwise) (parameter "signaturePropFile") or the properties inside the sig-prop file are invalid. Regards, Werner > -----Ursprüngliche Nachricht----- > Von: Ron Reynolds [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 1. Dezember 2005 23:17 > An: [email protected] > Betreff: No crypto protery file supplied to verify signature > > i am so close to getting my C# (WSE 3.0) client to connect to > my Axis 1.2.1 + > WSS4J server. i finally (i think) got all the C# issues > worked out and now > i'm back on the Java side with this - > > 1201:14:02:43 DEBUG org.apache.ws.security.WSSecurityEngine > :Verify XML Signature > 1201:14:02:43 DEBUG > org.apache.xml.security.algorithms.implementations.SignatureBa > seRSA :Created > SignatureDSA using SHA1withRSA > 1201:14:02:43 DEBUG > org.apache.ws.security.message.token.SecurityTokenReference > :Token reference > uri: #SecurityToken-7b111fac-a419-4ecd-8e01-c703d83fb85f > 1201:14:02:43 DEBUG org.apache.axis.EXCEPTIONS :AxisFault: > ... > WSDoAllReceiver: security processing failed; nested exception is: > org.apache.ws.security.WSSecurityException: General > security error > (WSSecurityEngine: No crypto protery file supplied to verify > signature) > at > org.apache.ws.axis.security.WSDoAllReceiver.invoke(WSDoAllRece > iver.java:160) > > i looked up what has Id "SecurityToken-7b111..." - it's a > very long 1-line > element > > <wsse:BinarySecurityToken > ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401 > -wss-x509-token-profile-1.0#X509v3" > EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200 401-wss-soap-message-security-1.0#Base64Binary" > xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401 > -wss-wssecurity-utility-1.0.xsd" > wsu:Id="SecurityToken-7b111fac-a419-4ecd-8e01-c703d83fb85f">MI IBjz...Az/lA==</wsse:BinarySecurityToken> > > that appears between the <wsse:UsernameToken> and the > <Signature> elements. > > i remember there was a discussion recently about the order of security > elements being very important to WSS4J - is this related to that? > > i'll start adding debug elements to my wss4j source, but just > in case someone > already knows this one i thought i'd ask. > > any help will be greatly appreciated. > > ................ron. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
