Re: [Axis2]is this [bug] already fixed?
Sorry guys! On 6/21/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: Hi Anamitra, Please use this wss4j-SNAPSHOT.jar from here [1] and replace your wss4j-SNAPSHOT.jar We had a problem in the wss4j-SNAPSHOT.jar in the axis2 nightly build and Dims just fixed it. Thanks Dims ! The next axis2 nightly build should have the correct jar with it. Thanks. Ruchith [1] http://people.apache.org/repository/wss4j/jars/ On 6/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi Ruchith > I downloaded the latest axis2 [nightly builds] and took the wss4jsnapshot > jar from there - still I got that same problem. Here is the scenario > > 1>I am doing only encryption from client to server and back ie there is > encryption from client to server and server back to client. > 2>In my tcpmon I see the client request go fine and the server is receives > and processes that fine. > 3>When the server is responding back I see a SignatureConfirmation element > there and the client errors out. > > I added the > false in client > inflow and then I stopped getting that error. But this works even for the > released axis2. So I am not sure what the "fix" is doing. Am I supposed to > set this enableSignatureConfirmation to false - without this its giving me > error. > > > > > Encrypt > > testme.PWCallbackClient > > testme/clientcrypto.properties > false > > false > true > > > > thanks > Anamitra > > > > "Ruchith > Fernando" >@gmail.com> axis-user@ws.apache.org > cc > 06/20/2006 07:07 > AMSubject >Re: [Axis2]is this [bug] already >fixed? > Please respond to > [EMAIL PROTECTED] > he.org > > > > > > > > Hi Anamitra, > > This was an issue in WSS4J [1] and now its fixed. > If you use the latest WSS4J (SVN head) you will be able aviode this > problem. > > Thanks, > Ruchith > > [1] http://issues.apache.org/jira/browse/WSS-44 > > On 6/19/06, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > > > Hi > > I was trying a 2 way encryption between a client and my service and the > > call ended with an exception as below. The client to server goes fine and > > the error comes when the server is sending back the encrypted response > back > > to the client. The tcp mon shows a SignatureConfirmation element in the > > response soap header and thats what probably the client side axis2 > receiver > > is cribbing abt! I remember seeing some emails on this before - I am > using > > axis2 released 1.0 version. If fixed can anyone tell me what I have to do > > to take the fix? > > > > thanks > > Anamitra > > > > [java] org.apache.axis2.AxisFault: WSHandler: Check Signature > > confirmation: > > got a SC element, but no stored SV; nested exception is: > > [java] org.apache.ws.security.WSSecurityException: WSHandler: > Check > > Sig > > ature confirmation: got a SC element, but no stored SV > > [java] at > > org.apache.axis2.security.WSDoAllReceiver.processMessage(WSDo > > llReceiver.java:336) > > [java] at > > org.apache.axis2.security.handler.WSDoAllHandler.invoke(WSDoA > > lHandler.java:82) > > [java] at org.apache.axis2.engine.Phase.invoke(Phase.java:381) > > [java] at > > org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473 > > > > [java] at > > org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:44 > > ) > > [java] at > > org.apache.axis2.description.OutInAxisOperationClient.send(Ou > > InAxisOperation.java:355) > > [java] at > > org.apache.axis2.description.OutInAxisOperationClient.execute > > OutInAxisOperation.java:279) > > [java] at > > org.apache.axis2.client.ServiceClient.sendReceive(ServiceClie > > t.java:457) > > [java] at > > org.apache.axis2.client.ServiceClient.sendReceive(ServiceClie > > t.java:399) > > [java] at testme.TestAxiom.main(TestAxiom.java:43) > > [java] Caused by: org.apache.ws.security.WSSecurityException: > > WSHandler: Ch > > ck Signature confirmation: got a SC element, but no stored SV > > [java] at > > org.apache.ws.securi
Re: [Axis2]is this [bug] already fixed?
Hi Anamitra,
Please use this wss4j-SNAPSHOT.jar from here [1] and replace your
wss4j-SNAPSHOT.jar
We had a problem in the wss4j-SNAPSHOT.jar in the axis2 nightly build
and Dims just fixed it. Thanks Dims ! The next axis2 nightly build
should have the correct jar with it.
Thanks.
Ruchith
[1] http://people.apache.org/repository/wss4j/jars/
On 6/20/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
Hi Ruchith
I downloaded the latest axis2 [nightly builds] and took the wss4jsnapshot
jar from there - still I got that same problem. Here is the scenario
1>I am doing only encryption from client to server and back ie there is
encryption from client to server and server back to client.
2>In my tcpmon I see the client request go fine and the server is receives
and processes that fine.
3>When the server is responding back I see a SignatureConfirmation element
there and the client errors out.
I added the
false in client
inflow and then I stopped getting that error. But this works even for the
released axis2. So I am not sure what the "fix" is doing. Am I supposed to
set this enableSignatureConfirmation to false - without this its giving me
error.
Encrypt
testme.PWCallbackClient
testme/clientcrypto.properties
false
false
true
thanks
Anamitra
"Ruchith
Fernando"
axis-user@ws.apache.org
cc
06/20/2006 07:07
AMSubject
Re: [Axis2]is this [bug] already
fixed?
Please respond to
[EMAIL PROTECTED]
he.org
Hi Anamitra,
This was an issue in WSS4J [1] and now its fixed.
If you use the latest WSS4J (SVN head) you will be able aviode this
problem.
Thanks,
Ruchith
[1] http://issues.apache.org/jira/browse/WSS-44
On 6/19/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Hi
> I was trying a 2 way encryption between a client and my service and the
> call ended with an exception as below. The client to server goes fine and
> the error comes when the server is sending back the encrypted response
back
> to the client. The tcp mon shows a SignatureConfirmation element in the
> response soap header and thats what probably the client side axis2
receiver
> is cribbing abt! I remember seeing some emails on this before - I am
using
> axis2 released 1.0 version. If fixed can anyone tell me what I have to do
> to take the fix?
>
> thanks
> Anamitra
>
> [java] org.apache.axis2.AxisFault: WSHandler: Check Signature
> confirmation:
> got a SC element, but no stored SV; nested exception is:
> [java] org.apache.ws.security.WSSecurityException: WSHandler:
Check
> Sig
> ature confirmation: got a SC element, but no stored SV
> [java] at
> org.apache.axis2.security.WSDoAllReceiver.processMessage(WSDo
> llReceiver.java:336)
> [java] at
> org.apache.axis2.security.handler.WSDoAllHandler.invoke(WSDoA
> lHandler.java:82)
> [java] at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
> [java] at
> org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473
>
> [java] at
> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:44
> )
> [java] at
> org.apache.axis2.description.OutInAxisOperationClient.send(Ou
> InAxisOperation.java:355)
> [java] at
> org.apache.axis2.description.OutInAxisOperationClient.execute
> OutInAxisOperation.java:279)
> [java] at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClie
> t.java:457)
> [java] at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClie
> t.java:399)
> [java] at testme.TestAxiom.main(TestAxiom.java:43)
> [java] Caused by: org.apache.ws.security.WSSecurityException:
> WSHandler: Ch
> ck Signature confirmation: got a SC element, but no stored SV
> [java] at
> org.apache.ws.security.handler.WSHandler.checkSignatureConfir
> ation(WSHandler.java:294)
> [java] at
> org.apache.axis2.security.WSDoAllReceiver.processMessage(WSDo
> llReceiver.java:196)
> [java] ... 9 more
>
>
> -
> 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]
-
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]
Re: [Axis2]is this [bug] already fixed?
Hi Ruchith
I downloaded the latest axis2 [nightly builds] and took the wss4jsnapshot
jar from there - still I got that same problem. Here is the scenario
1>I am doing only encryption from client to server and back ie there is
encryption from client to server and server back to client.
2>In my tcpmon I see the client request go fine and the server is receives
and processes that fine.
3>When the server is responding back I see a SignatureConfirmation element
there and the client errors out.
I added the
false in client
inflow and then I stopped getting that error. But this works even for the
released axis2. So I am not sure what the "fix" is doing. Am I supposed to
set this enableSignatureConfirmation to false - without this its giving me
error.
Encrypt
testme.PWCallbackClient
testme/clientcrypto.properties
false
false
true
thanks
Anamitra
"Ruchith
Fernando"
axis-user@ws.apache.org
cc
06/20/2006 07:07
AMSubject
Re: [Axis2]is this [bug] already
fixed?
Please respond to
[EMAIL PROTECTED]
he.org
Hi Anamitra,
This was an issue in WSS4J [1] and now its fixed.
If you use the latest WSS4J (SVN head) you will be able aviode this
problem.
Thanks,
Ruchith
[1] http://issues.apache.org/jira/browse/WSS-44
On 6/19/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> Hi
> I was trying a 2 way encryption between a client and my service and the
> call ended with an exception as below. The client to server goes fine and
> the error comes when the server is sending back the encrypted response
back
> to the client. The tcp mon shows a SignatureConfirmation element in the
> response soap header and thats what probably the client side axis2
receiver
> is cribbing abt! I remember seeing some emails on this before - I am
using
> axis2 released 1.0 version. If fixed can anyone tell me what I have to do
> to take the fix?
>
> thanks
> Anamitra
>
> [java] org.apache.axis2.AxisFault: WSHandler: Check Signature
> confirmation:
> got a SC element, but no stored SV; nested exception is:
> [java] org.apache.ws.security.WSSecurityException: WSHandler:
Check
> Sig
> ature confirmation: got a SC element, but no stored SV
> [java] at
> org.apache.axis2.security.WSDoAllReceiver.processMessage(WSDo
> llReceiver.java:336)
> [java] at
> org.apache.axis2.security.handler.WSDoAllHandler.invoke(WSDoA
> lHandler.java:82)
> [java] at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
> [java] at
> org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473
>
> [java] at
> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:44
> )
> [java] at
> org.apache.axis2.description.OutInAxisOperationClient.send(Ou
> InAxisOperation.java:355)
> [java] at
> org.apache.axis2.description.OutInAxisOperationClient.execute
> OutInAxisOperation.java:279)
> [java] at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClie
> t.java:457)
> [java] at
> org.apache.axis2.client.ServiceClient.sendReceive(ServiceClie
> t.java:399)
> [java] at testme.TestAxiom.main(TestAxiom.java:43)
> [java] Caused by: org.apache.ws.security.WSSecurityException:
> WSHandler: Ch
> ck Signature confirmation: got a SC element, but no stored SV
> [java] at
> org.apache.ws.security.handler.WSHandler.checkSignatureConfir
> ation(WSHandler.java:294)
> [java] at
> org.apache.axis2.security.WSDoAllReceiver.processMessage(WSDo
> llReceiver.java:196)
> [java] ... 9 more
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
Re: [Axis2]is this [bug] already fixed?
Hi Anamitra, This was an issue in WSS4J [1] and now its fixed. If you use the latest WSS4J (SVN head) you will be able aviode this problem. Thanks, Ruchith [1] http://issues.apache.org/jira/browse/WSS-44 On 6/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi I was trying a 2 way encryption between a client and my service and the call ended with an exception as below. The client to server goes fine and the error comes when the server is sending back the encrypted response back to the client. The tcp mon shows a SignatureConfirmation element in the response soap header and thats what probably the client side axis2 receiver is cribbing abt! I remember seeing some emails on this before - I am using axis2 released 1.0 version. If fixed can anyone tell me what I have to do to take the fix? thanks Anamitra [java] org.apache.axis2.AxisFault: WSHandler: Check Signature confirmation: got a SC element, but no stored SV; nested exception is: [java] org.apache.ws.security.WSSecurityException: WSHandler: Check Sig ature confirmation: got a SC element, but no stored SV [java] at org.apache.axis2.security.WSDoAllReceiver.processMessage(WSDo llReceiver.java:336) [java] at org.apache.axis2.security.handler.WSDoAllHandler.invoke(WSDoA lHandler.java:82) [java] at org.apache.axis2.engine.Phase.invoke(Phase.java:381) [java] at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473 [java] at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:44 ) [java] at org.apache.axis2.description.OutInAxisOperationClient.send(Ou InAxisOperation.java:355) [java] at org.apache.axis2.description.OutInAxisOperationClient.execute OutInAxisOperation.java:279) [java] at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClie t.java:457) [java] at org.apache.axis2.client.ServiceClient.sendReceive(ServiceClie t.java:399) [java] at testme.TestAxiom.main(TestAxiom.java:43) [java] Caused by: org.apache.ws.security.WSSecurityException: WSHandler: Ch ck Signature confirmation: got a SC element, but no stored SV [java] at org.apache.ws.security.handler.WSHandler.checkSignatureConfir ation(WSHandler.java:294) [java] at org.apache.axis2.security.WSDoAllReceiver.processMessage(WSDo llReceiver.java:196) [java] ... 9 more - 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]
