Hello
I'musing cxf 2.3.1 because we use a jboss 6.0.0.Final
I have  wsdl with a policy:
                                <sp:EndorsingSupportingTokens>
                                        <wsp:Policy>
                                                <sp:X509Token
sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient";>
                                                        <wsp:Policy>
                                                                
<sp:WssX509V3Token10 />
                                                        </wsp:Policy>
                                                </sp:X509Token>
                                        </wsp:Policy>
                                </sp:EndorsingSupportingTokens>
                                <sp:SignedSupportingTokens>
                                        <wsp:Policy>
                                                <sp:UsernameToken
sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient";>
                                                        <wsp:Policy>
                                                                
<sp:WssUsernameToken10 />
                                                        </wsp:Policy>
                                                </sp:UsernameToken>
                                        </wsp:Policy>
                                </sp:SignedSupportingTokens>

The client signs the message and the server receives it: 
When the server receives it it gets a
java.lang.NullPointerException at
org.apache.ws.security.message.token.X509Security.getX509Certificate

The server endpoint is configured like:

        <jaxws:endpoint 
                id="careReceiverInsurabilityWSServer" 
                          ....
                <jaxws:properties>
                        <entry key="ws-security.callback-handler"
value="poc.samples.jboss.cxf.ejb.sync.security.policy.webservice.callbackHandlers.server.UsernameTokenCallbackHandlerServer"/>
                        <entry key="ws-security.signature.properties"
value="security/serverSignVerify.properties"/>
                        <entry key="ws-security.signature.username" 
value="clienttrusted"/>
        </jaxws:properties>
        </jaxws:endpoint>

my security/serverSignVerify.properties contains: 
org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
org.apache.ws.security.crypto.merlin.keystore.type=jks
org.apache.ws.security.crypto.merlin.keystore.password=storepassword
org.apache.ws.security.crypto.merlin.keystore.alias=clienttrusted
org.apache.ws.security.crypto.merlin.file=security/server-truststore.jks

when I debug I see that the crypto of the X509Security is null.
I think the problem is the 'ws-security.signature.properties' key that is
not found.
Could that be possible ?
even though the client side is conigure like that and it can find it.

I will continue debugging or maybe i someone knows the answer would be
great:
thanks






--
View this message in context: 
http://cxf.547215.n5.nabble.com/ws-security-signature-properties-throws-a-org-apache-ws-security-message-token-X509Security-getX509Cn-tp4682219p4682219.html
Sent from the cxf-dev mailing list archive at Nabble.com.

Reply via email to