Am using WebMethods IS 9.6 CoreFix 12 on Windows 8.1
Produced a WSD using a client WSDL and Schema.
Declared their certificate via a WSC Endpoint and linked policy X509 Authentication and Signature to the WSC. This produces a message with complete certification.
As the customer specifically requires
I created custom X509V3Authentication_Signature policy based upon the original which works nicely.
They now report that this generates more signatures (references) in the security header than are permitted at their end. The signatures are generated for the soap bdy (permitted) and timestamp and #X509- Key info (not permitted). Is there anyway that one might restrict these other reference entries in the final soap message through a revised policy or other means?