[Issue 1297] New - Scenario 1 in trust "jsr109interop-s-s-m" & "jsr109interop-s-m-m" fails with SOAPFaultException: An error occurred when verifying security for the message.

[anand_mishra]

https://wsit.dev.java.net/issues/show_bug.cgi?id=1297
                 Issue #|1297
                 Summary|Scenario 1 in trust "jsr109interop-s-s-m" & "jsr109int
                        |erop-s-m-m" fails with SOAPFaultException: An error oc
                        |curred when verifying security for the message.
               Component|wsit
                 Version|2.0
                Platform|All
              OS/Version|All
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|tests
             Assigned to|anand_mishra
             Reported by|anand_mishra






------- Additional comments from anand_mishra@... Tue Nov  3 05:07:05 +0000 2009 -------
Scenario 1 in trust "jsr109interop-s-s-m" & "jsr109interop-s-m-m" fails with
SOAPFaultException: An error occurred when verifying security for the message.

This could be test config issue.

Soap log is attached and required ms-service-e2e log.

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...

[anand_mishra]

https://wsit.dev.java.net/issues/show_bug.cgi?id=1297






------- Additional comments from anand_mishra@... Tue Nov  3 05:11:41 +0000 2009 -------
Created an attachment (id=1044)
soap-log


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...

[jdg6688]

https://wsit.dev.java.net/issues/show_bug.cgi?id=1297






------- Additional comments from jdg6688@... Tue Nov  3 21:49:56 +0000 2009 -------
This is an know issue from WCF. The policy in the wsdl
has any extra
 <sp:SignedParts>
                            <sp:Header Name="To"
Namespace="http://www.w3.org/2005/08/addressing"/>
                        </sp:SignedParts>
in the EndorsingSupportingToken but they don't use it.

To get around the issue:
1. Remove
 <sp:SignedParts>
                            <sp:Header Name="To"
Namespace="http://www.w3.org/2005/08/addressing"/>
                        </sp:SignedParts>

from the EndorsingSupportingToken in the local wsdl PingService.wsdl.

2. point to the local wsdl in creating the client.


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...