Re: WS-Security Issue with upgrading from CXF 2.3.3. to CXF 2.4.1

2011-07-05 Thread Colm O hEigeartaigh
Hi Srinivas, You must use the USER property to configure the keystore alias when you are only doing signature. SIGNATURE_USER comes in to play in the scenario of (e.g.) a UsernameToken and a Signature, when you specify the username of the UsernameToken via USER, and the keystore alias via SIGNATUR

Re: WS-Security Issue with upgrading from CXF 2.3.3. to CXF 2.4.1

2011-07-04 Thread srinivas thallapalli
Hi Colm, Actually I am configuring UsernameToken, Encrypt and Signature standards for my cxf webservice. With 2.3.7 version of CXF everything working fine. Upgrading to 2.4.1 causing this issue, the keystores and configurations files are same. With my investigation, I suspect there is conflict is

Re: WS-Security Issue with upgrading from CXF 2.3.3. to CXF 2.4.1

2011-07-04 Thread Colm O hEigeartaigh
Hi Srinivas, It's most probably one of the following scenarios: 1) The keystore alias you have specified is incorrect. Try checking your keystore, i.e. keytool -list -keystore sws-client-keystore.jks, and see if the alias you have configured in the properties file is shown. 2) Check the keystore

Re: WS-Security Issue with upgrading from CXF 2.3.3. to CXF 2.4.1

2011-07-03 Thread srinivas thallapalli
Hi All, Any sugesstions on this issue. Thanks -- View this message in context: http://cxf.547215.n5.nabble.com/WS-Security-Issue-with-upgrading-from-CXF-2-3-3-to-CXF-2-4-1-tp4541788p4548938.html Sent from the cxf-user mailing list archive at Nabble.com.

Re: WS-Security Issue with upgrading from CXF 2.3.3. to CXF 2.4.1

2011-07-01 Thread srinivas thallapalli
Hi Colm, Please have a look at my properties again, I do not have any slashes. Thanks -- View this message in context: http://cxf.547215.n5.nabble.com/WS-Security-Issue-with-upgrading-from-CXF-2-3-3-to-CXF-2-4-1-tp4541788p4542720.html Sent from the cxf-user mailing list archive at Nabble.com.

Re: WS-Security Issue with upgrading from CXF 2.3.3. to CXF 2.4.1

2011-07-01 Thread Colm O hEigeartaigh
This looks suspect: > org.apache.ws.security.crypto.merlin.keystore.alias=/sws-client-privatekey/ Try removing the forward slashes. Colm. On Fri, Jul 1, 2011 at 1:16 PM, srinivas thallapalli wrote: > Hi Colm, > > Sincere apologies. I have duplicate classpath entry for wss4j 1.5.10, that > is t

Re: WS-Security Issue with upgrading from CXF 2.3.3. to CXF 2.4.1

2011-07-01 Thread srinivas thallapalli
Hi Colm, Sincere apologies. I have duplicate classpath entry for wss4j 1.5.10, that is the issue. On removal of that duplicate entry. I am getting problem with Signature while getting private for my alias. This alias is mentioned in configuration property file and keystore contains key for this al

Re: WS-Security Issue with upgrading from CXF 2.3.3. to CXF 2.4.1

2011-07-01 Thread Colm O hEigeartaigh
Hi, Could you check your classpath again - WSSecurityUtil has the following method in WSS4J 1.6: static int decodeAction(java.lang.String action, java.util.List actions, WSSConfig wssConfig) http://ws.apache.org/wss4j/apidocs/org/apache/ws/security/util/WSSecurityUtil.html Colm. On Fri, Jul 1

WS-Security Issue with upgrading from CXF 2.3.3. to CXF 2.4.1

2011-07-01 Thread srinivas thallapalli
Hi All I am trying to upgrade CXF 2.3.3 to CXF 2.4.1, I am facing some WS-Security issues with my application which worked fine with 2.3.3. I am using wss4j-1.6.1.jar which is distributed with CXF 2.4.1. The following is the exception stack trace. /Caused by: java.lang.NoSuchMethodError: org.apa