Uncomment MessageCredentialType.IssuedToken for WSHttpBinding

[emre-toraman]

Fixes #1317

[emre-toraman]

@dotnet-policy-service agree company="SOTI"

[emre-toraman]

@birojnayak Thank you for your comment in #1317 (comment), I created the PR as you suggested. Can you please review and advise?

[g7ed6e]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[birojnayak]

@emre-toraman have you tested internally ? Is there a possibility to add test ?

[emre-toraman]

@birojnayak I have tested two things internally:

• I was able to start WebApplication with a service that uses

var httpBinding = new WSHttpBinding(SecurityMode.TransportWithMessageCredential);
httpBinding.Security.Message.ClientCredentialType = MessageCredentialType.IssuedToken;

• I was able to create binding elements from above binding and use that collection to create a CustomBinding:

var bindingElementCollection = httpBinding.CreateBindingElements()

I'm not sure how to create a client for this service though. Do you have any client sample for this configuration?

[birojnayak]

@emre-toraman I assume you have a client which is connecting to your existing WCF service, you can run the same client pointing to CoreWCF service. If that works let me know, happy to approve the PR.

I understand testing token is bit tricky and needs set up. While porting WS-Fed binding, I had written some test here. See if this could be useful.