Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add API T:System.ServiceModel.Channels.ISecurityCapabilities #1415

Closed
zhenlan opened this issue Jul 29, 2016 · 6 comments
Closed

Add API T:System.ServiceModel.Channels.ISecurityCapabilities #1415

zhenlan opened this issue Jul 29, 2016 · 6 comments
Assignees
Labels
feature request Adding new functionality requiring adding an API to the public contract.

Comments

@zhenlan
Copy link
Member

zhenlan commented Jul 29, 2016

This API has dependency on System.Net.ProtectionLevel

@roncain roncain self-assigned this Aug 3, 2016
@zhenlan zhenlan added this to the 1.1.0 milestone Aug 3, 2016
@zhenlan zhenlan modified the milestones: 1.1.0, 1.2.0 Aug 26, 2016
@roncain
Copy link
Contributor

roncain commented Sep 23, 2016

Interface is already in our code base. Remaining work is to expose it. Recommend System.ServiceModel.Security contract.

@roncain
Copy link
Contributor

roncain commented Oct 17, 2016

Tasks are:

  • Add implementation [already in code base]
  • Add to contract [waiting for ProtectionLevel to be available in NET Native contract]
  • Add unit tests
  • Add scenario tests (may require adding add'l use of implementation throughout product)

@StephenBonikowsky
Copy link
Member

ProtectionLevel is planned for netstandard 2.0 but not in yet.

@zhenlan
Copy link
Member Author

zhenlan commented Jan 20, 2017

We will resume this work when ProtetionLevel is available on UWP/NS2.0.

@zhenlan zhenlan modified the milestones: 2.1.0, 2.0.0 May 5, 2017
@zhenlan zhenlan modified the milestones: 2.1.0, Future Mar 5, 2018
@Lxiamail Lxiamail added the feature request Adding new functionality requiring adding an API to the public contract. label May 21, 2018
@Lxiamail Lxiamail modified the milestones: Future, 3.0 May 25, 2018
@StephenBonikowsky
Copy link
Member

Unit tests and scenario tests are not necessary.
This interface is exercised automatically with all of our existing tests that use ChannelFactory.

@StephenBonikowsky
Copy link
Member

One correction, added unit tests.
PR #3329

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Adding new functionality requiring adding an API to the public contract.
Projects
None yet
Development

No branches or pull requests

4 participants