[P2] Support System.ServiceModel.Channels.SecurityBindingElement

[StephenBonikowsky]

APIs	Port/Implement	Public Contract	Testing
property SecurityAlgorithmSuite DefaultAlgorithmSuite	Merged	Added	Unit Scenario
property SecurityKeyEntropyMode KeyEntropyMode	Merged	Added	Unit Scenario

---

API Notes

---

Implementation Notes
Already ported.

---

Public Contract Notes

• Public Contract: System.ServiceModel.Security

---

Testing Notes

• Unit tests are required : PR Add unit tests for S.SM.Security.SecurityAlgorithmSuite #3915, Unit test for SecurityBindingElement.KeyEntropyMode. #3916.
• Scenario tests needed: ???

---

PR Links
DefaultAlgorithmSuite was added to PC via: #3875
KeyEntropyMode was added to PC via: #3900
Scenario tests tracked by: #4022

[krispenner]

Hi @StephenBonikowsky,

Will this also add support for the derived class AsymmetricSecurityBindingElement?

For example, below is effectively the one and only code block that is preventing us from targeting .NET Standard and running on .NET Core. I would be forever grateful if this would be supported with your upcoming release in some way.

var messageSecurity = new AsymmetricSecurityBindingElement()
{
    MessageSecurityVersion = MessageSecurityVersion.WSSecurity11WSTrustFebruary2005WSSecureConversationFebruary2005WSSecurityPolicy11,
    InitiatorTokenParameters = new X509SecurityTokenParameters { InclusionMode = SecurityTokenInclusionMode.Never },
    RecipientTokenParameters = new X509SecurityTokenParameters { InclusionMode = SecurityTokenInclusionMode.Never },
    MessageProtectionOrder = MessageProtectionOrder.SignBeforeEncrypt,
    EnableUnsecuredResponse = true,
    IncludeTimestamp = false,
    DefaultAlgorithmSuite = SecurityAlgorithmSuite.Basic128Rsa15,
};
messageSecurity.SetKeyDerivation(false);
messageSecurity.EndpointSupportingTokenParameters.Signed.Add(new X509SecurityTokenParameters());

[mconnew]

@krispenner, I have a concern about whether that will enable you because you are setting the MessageProtectionOrder. That implies you are using security mode Message, but we can only support TransportWithMessageCredential (which doesn't sign or encrypt the message). Can you please provide you complete binding configuration so I can validate that there's nothing else missing.
We also don't have tests for the various MessageSecurityVersion's that are possible so we might need to fill out some functionality to support your exact use case, which means we need to write a test for your scenario. What kind of credentials are you using?