I have two services communicating, messages in both ways have to be secured. Signed and encrypted but let's go step by step.
Each one has it's own private key (in the keystore), and it's public key exported into the other one's keystore. So, client signs with his own private key and encrypts with the public key of the server. The server decrypts the message using his own private key and then validates the message using client's public key in his keystore. Then server doeas just what the client did but using his keys, and that's it.
I managed to get this to work with xwss security interceptor from spring-ws 1.0.3 using some aditional code.
Tried to port it to 1.5 (just by changing jars) but it didn't work. Okay, things were changed, so what, let's make it work. But I just couldn't (even after a couple of hours in the debug mode and constantly altering the policy file), server was very persistent not wanting to validate client's signature (I left out the encryption in this scenario for simplicity's sake).
So I said, ok, let's go to wss4j interceptor. Don't know if I like the property-only configuration over xwss policy, but suppose it's easyer for beginners.
Okay, I wired in the interceptor, crypto objects, keystorehandler (yes, the new one from wss4j package), all the passwords, the keystores remained the same on both ends.
I just applied signing and verification. The exception I get is this:Code:
2008.04.11 18:53:37 org.apache.xml.security.signature.Reference verify
WARNING: Verification failed for URI quot;#id-19350739quot;
2008.04.11 18:53:37 org..ws.soap.security.AbstractWsSecurityInterceptor handleValidationException
WARNING: Could not validate request: The signature verification failed; nested exception is org.apache.ws.security.WSSecurityException: The signature verification failed
Got armed with sources from everywhere so i can see code
The problem is in the Reference class, where the digests (the one that came with the message and the new computed one) get compared and they were not the same. Code: byte[] elemDig = this.getDigestValue(); byte[] calcDig = this.calculateDigest(); boolean equal = MessageDigestAlgorithm.isEqual(elemDig, calcDig);
... from org.apache.xml.security.signature.Reference.verify ()
I did fetch the right key from the keystore since his and clients serial number are the same.
Then I read in the WS documentation that only SHA1 with RSA algorithm is supported and that's exactly the kind of keys I have (1024 bits, don't know if it's important).
And finaly, the server configuration, but I don't think that there's anything wrong here.Code:
lt;bean class=quot;org..ws.soap.server.endpoint.mapping.SoapActionEndpointMappingquot;gt;
lt;property name=quot;mappingsquot;gt;
lt;propsgt;
lt;prop key=quot;partRequestquot;gt;partEndpointDom4jlt;/propgt;
lt;prop key=quot;statsRequestquot;gt;statsEndpointlt;/propgt;
lt;/propsgt;
lt;/propertygt;
lt;property name=quot;interceptorsquot;gt;
lt;listgt;
lt;ref bean=quot;signatureInterceptorquot;/gt;
lt;bean class=quot;org..ws.server.endpoint.interceptor.PayloadLoggingInterceptorquot; /gt;
lt;/listgt;
lt;/propertygt;
lt;/beangt;
lt;bean id=quot;signatureInterceptorquot; class=quot;org..ws.soap.security.wss4j.Wss4jSecurityInterceptorquot;gt;
lt;property name=quot;validationActionsquot; value=quot;Signaturequot;gt;lt;/propertygt;
lt;property name=quot;validationSignatureCryptoquot; ref=quot;serverKeystorequot;gt;lt;/propertygt;
lt;/beangt;
lt;bean id=quot;serverKeystorequot; class=quot;org..ws.soap.security.wss4j.support.CryptoFactoryBeanquot;gt;
lt;property name=quot;keyStorePasswordquot; value=quot;store_password_serverquot;/gt;
lt;property name=quot;keyStoreLocationquot; value=quot;classpath:/security/serverKeystore.jksquot;/gt;
lt;/beangt;
Any help will be greatly appreciated.
Yeah, and when only trying to encrypt i get the encrypted message in the endpoint, no decryption has ever taken place.
Configuration:Code:
lt;bean class=quot;org..ws.soap.server.endpoint.mapping.SoapActionEndpointMappingquot;gt;
lt;property name=quot;mappingsquot;gt;
lt;propsgt;
lt;prop key=quot;partRequestquot;gt;partEndpointDom4jlt;/propgt;
lt;prop key=quot;statsRequestquot;gt;statsEndpointlt;/propgt;
lt;/propsgt;
lt;/propertygt;
lt;property name=quot;interceptorsquot;gt;
lt;listgt;
lt;ref bean=quot;encryptionInterceptorquot;/gt;
lt;bean class=quot;org..ws.server.endpoint.interceptor.PayloadLoggingInterceptorquot; /gt;
lt;/listgt;
lt;/propertygt;
lt;/beangt;
lt;bean id=quot;encryptionInterceptorquot; class=quot;org..ws.soap.security.wss4j.Wss4jSecurityInterceptorquot;gt;
lt;property name=quot;validationActionsquot; value=quot;Encryptquot;gt;lt;/propertygt;
lt;property name=quot;validationDecryptionCryptoquot; ref=quot;serverKeystorequot;gt;lt;/propertygt;
lt;property name=quot;validationCallbackHandlerquot; ref=quot;keyStoreHandlerquot;gt;lt;/propertygt;
lt;/beangt;
lt;bean id=quot;serverKeystorequot; class=quot;org..ws.soap.security.wss4j.support.CryptoFactoryBeanquot;gt;
lt;property name=quot;keyStorePasswordquot; value=quot;store_password_serverquot;/gt;
lt;property name=quot;keyStoreLocationquot; value=quot;classpath:/security/serverKeystore.jksquot;/gt;
lt;/beangt;
lt;bean id=quot;keyStoreHandlerquot; class=quot;org..ws.soap.security.wss4j.callback.KeyStoreCallbackHandlerquot;gt;
lt;property name=quot;privateKeyPasswordquot; value=quot;key_password_serverquot;/gt;
lt;property name=quot;keyStorequot; ref=quot;keyStorequot;/gt;
lt;/beangt;
lt;bean id=quot;keyStorequot;class=quot;org..ws.soap.security.support.KeyStoreFactoryBeanquot;gt;
lt;property name=quot;passwordquot; value=quot;store_password_serverquot; /gt;
lt;property name=quot;locationquot; value=quot;classpath:security/serverKeystore.jksquot; /gt;
lt;/beangt;Still nothing. I've placed all the right jars in classpath, the keystores and all passwords are correct (the setup i have with spring ws 1.0.3. and xwss works with those exact keystores) but still no go (even tried to place wss4j 1.5.3. in classpath as someone suggested in some other thread). Don't really know what else to do.
dspoljaric,
I got digi sigs working by following these steps
showthread.php?t=52204
I generated the .jks as in the example as well - might be worth checking out, how much trouble is it to re generate the keys?
I worked on this same problem for a few days. The only way I could get certificate authentication working (using wss4j or xwss) with spring ws 1.5.0 was to use SAAJ 1.3 on the client and set the client's transformer factory with
-Djavax.xml.transform.TransformerFactory=org.apache .xalan.xsltc.trax.TransformerFactoryImpl
This transformer exists in the xalan 2.7.0 jar but it's not the default.
My guess is that some transformers are modifying the message AFTER the digest is created and therefore, as you pointed out, they do not match when compared on the service side. Again, that's just a guess.
Can you try using SAAJ 1.3 and this transformer on your client and post the result?
dspoljaric,
Can you post your whole classpath - wss4j only works with spring ws 1.5 and the dependencies have to be correct as stated, has to be saaj 1.3 and jaxp 1.3 as well i think
.apache.xalan.internal.xsltc.trax.Trans formerImpl in the end of the com.sun.xml.messaging.saaj.util.transform.Efficien tStreamingTransformer.transform(Source, Result) method.
The transformers on the client side change the message. But, the transformers on the server side also change the message, and finaly the digest value before client transformation and after server transformation are the same.
Changing the transformer factory had no effect. Transformation results were different but digest value stayed the same on both ends.
That said, here is my classpath (client and server classpath are the same for simplicity's sake)
activation-1.1.1.jar
bcprov-jdk13-132.jar
castor-1.1.2.jar
commons-logging.jar
dom4j-1.6.1.jar
jdom.jar
jsr173_1.0_api.jar
jstl.jar
junit.jar
mail-1.4.1.jar
ognl-2.6.9.jar
opensaml-1.1.jar
saaj-api-1.3.jar
saaj-impl-1.3.jar
serializer.jar
spring-binding-1.0.5.jar
spring-webflow-1.0.5.jar
spring-webmvc.jar
spring-ws-1.5.0.jar
spring-xml-1.5.0.jar
spring.jar
standard.jar
wsdl4j-1.6.1.jar
wss4j-1.5.4.jar
xalan-2.7.0.jar
xercesImpl-2.8.1.jar
xmlsec-1.4.0.jar
Guess I have to digg even deeper...
the only immediate difference i can see is that in my class path i have the JAXP 1.3 jars downloaded from servlets/P... 4amp;folderID=0
its worth a shot
Switching the jars made validation work, but some other problems came with it.
I'm using CastorMarshaller, version 1.1.2., and it needs xalan and xerces jars from spring ws distribution, and as soon as I put them in the lib directory verification goes to fail mode.
So from now on it's a marshaller problem and that can be fixed easy
Note that I've found a bug which resulted in invalid signatures being created when using WSS4J and SAAJ. It's quite a subtle bug, caused by the DOM Document provided by SAAJ not being in sync with the SAAJ SOAPMessage. Took me 12 hours to find .
See browse/SWS-345.
As a workaround, you can use Axiom, rather than SAAJ, or wait for 1.5.1 (to be released somewhere this weekend). |
Post at 2011-4-15 14:33
| This Author's Posts Only
