.NET Core 3.1 X509 signature

I’m having a problem with signing WCF calls with a X509 certificate signature.

The following code works with .NET Framework but it doesn’t with .NET Core because X509SecurityToken doesn’t exist and I can’t access the RequestSoapContext.

SvcService.Service ws = new SvcService.Service();
X509Certificate2 cert = new X509Certificate2("cert.pfx", 
"privatekeypassword");
X509SecurityToken token = new X509SecurityToken(cert);
 ws.RequestSoapContext.Security.Tokens.Add(token);
 ws.RequestSoapContext.Security.Elements.Add(new MessageSignature(token));
 
 DataSet ds = ws.GetItem(2081234);

What would be the method to achieve the same in .NET Core? The proxy classes are generated with dotnet-svcutil.

[mconnew]

The content type application/soap+xml is for SOAP 1.2 and text/xml is for SOAP 1.1. So your service is returning a SOAP 1.2 response. You can either modify your binding or create a new binding and setting the appropriate message version on the TextMessageEncodingBindingElement. I suspect the following binding should work for you:

var mebe = new TextMessageEncodingBindingElement();
mebe.MessageVersion = MessageVersion.Soap12;
var transportbe = new HttpTransportBindingElement();
var binding = new CustomBinding(mebe, transportbe);

If not, then use:

var customBinding = new CustomBinding(existingBinding);
var mebe = customBinding.Elements.Find<TextMessageEncodingBindingElement>();
mebe.MessageVersion = MessageVersion.Soap12;

And use the customBinding when creating your channel factory.

[domagojmedo]

@mconnew is there any plan to enable this signing on .NET Core? I see that you commented that you would like to include it, but issue has since been closed