I am configuring WCF to talk to non-.NET SOAP Framework.
The SOAP message will be encrypted with public-key, with Timestamp and UsernameToken in the Security Header.
I am starting off with CreateAnonymousForCertificateBindingElement(), and adding UserNameSecurityTokenParameters() to EndpointSupportingTokenParameters.Signed collection.
Difficulty is: In the SOAP Security Header I get ONE EncryptedData element that is giving the 3rd party service trouble... If I use a tool to submit altered SOAP Envelope without EncryptedData element (which seems to be not needed) the 3rd party service
takes the request successfuly.
1) What may be generating this EncryptedData element?
2) How could EncryptedData be turned off OR removed from the Security Header?
View Complete Post