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.

Sign up for GitHub

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

Jump to bottom

Support DnsEndpointIdentity #12

Closed
iamjasonp opened this issue May 13, 2015 · 7 comments
Closed

Support DnsEndpointIdentity #12

iamjasonp opened this issue May 13, 2015 · 7 comments
Assignees
@hongdai
Milestone
2015.10

Comments

@iamjasonp
Copy link
Member

DnsEndpointIdentity currently throws PlatformNotSupportedException.
@zhenlan
Copy link
Member

zhenlan commented Jul 14, 2015

This is currently pending the availability of TokenManager

@zhenlan
Copy link
Member

zhenlan commented Jul 14, 2015

@hongdai will work with @mconnew and add tests to see what are involved to enable this feature.

@zhenlan zhenlan added this to the 1.0.0-beta7 milestone Jul 14, 2015
@hongdai
Copy link
Contributor

hongdai commented Jul 28, 2015

After discuss with Matt, I will:
1 add a scenario test to test DnsEndpointIdentity E2E
2. Create a feature item to track DnsEndpointIdentity can be created, serialized and deserialized correctly. This combines #13 should enable the feature.

@hongdai hongdai mentioned this issue Jul 28, 2015
Closed
@hongdai
Copy link
Contributor

hongdai commented Jul 31, 2015

There are two major E2E scenarios, both are blocked because of dependent features are not available yet.
Scenario 1: Verify Server identity for WS* binding. This is blocked by WS*binding is not supported yet. Tracked by issue #31.
Scenario 2: Verify Server identity for NetTcpBinding when SecurityMode is on. SecurityMode on is not supported yet. tracked by issue #81 .

@hongdai
Copy link
Contributor

hongdai commented Aug 4, 2015

I have implemented a positive E2E Scenario 2. Once the feature is fully enabled. I will add negative scenario tests.

@hongdai hongdai mentioned this issue Aug 4, 2015
Merged
@zhenlan zhenlan modified the milestones: 1.0.0-beta7, 2015.08 Aug 4, 2015
@zhenlan zhenlan assigned mconnew and unassigned hongdai Aug 4, 2015
@iamjasonp
Copy link
Member Author

This may start coming through as part of my large change to turn on SslStream. Stay tuned on this.

@iamjasonp iamjasonp mentioned this issue Aug 31, 2015
Merged
@zhenlan zhenlan modified the milestones: 2015.09, 2015.08 Sep 1, 2015
iamjasonp added a commit to iamjasonp/wcf that referenced this issue Sep 2, 2015
@iamjasonp
Add transport security support for net.tcp
9e1585c 
* Add support for SecurityMode.Transport in net.tcp
* Add in support for client X509Certificates for WCF Core
* Add StreamSecurityBindingElement
* Add SslStreamSecurity and supporting components
* Add WindowsStreamSecurity stubs
* Import IdentityModel code around X509 cert, tokens
* Disable failing tests due to WindowsStreamSecurity being stubbed now (dotnet#301)
* Add support for DnsEndpointIdentity

Fixes dotnet#9, dotnet#12, dotnet#81
iamjasonp added a commit to iamjasonp/wcf that referenced this issue Sep 2, 2015
@iamjasonp
Add transport security support for net.tcp
d5eaa9c 
* Add support for SecurityMode.Transport in net.tcp
* Add in support for client X509Certificates for WCF Core
* Add StreamSecurityBindingElement
* Add SslStreamSecurity and supporting components
* Add WindowsStreamSecurity stubs
* Import IdentityModel code around X509 cert, tokens
* Add support for DnsEndpointIdentity
* Disable failing tests due to WindowsStreamSecurity being stubbed now (dotnet#301)
* Cleanup of Tcp ClientCredentialType tests
* Update project.lock.json files for new dependencies

Fixes dotnet#9, dotnet#12, dotnet#81
@iamjasonp iamjasonp mentioned this issue Sep 2, 2015
Merged
iamjasonp added a commit to iamjasonp/wcf that referenced this issue Sep 2, 2015
@iamjasonp
Add transport security support for net.tcp
56a4255 
* Add support for SecurityMode.Transport in net.tcp
* Add in support for client X509Certificates for WCF Core
* Add StreamSecurityBindingElement
* Add SslStreamSecurity and supporting components
* Add WindowsStreamSecurity stubs
* Import IdentityModel code around X509 cert, tokens
* Add support for DnsEndpointIdentity
* Disable failing tests due to WindowsStreamSecurity being stubbed now (dotnet#301)
* Cleanup of Tcp ClientCredentialType tests
* Update project.lock.json files for new dependencies

Fixes dotnet#9, dotnet#12, dotnet#81
@hongdai hongdai mentioned this issue Sep 8, 2015
Closed
@zhenlan zhenlan modified the milestones: 2015.10, 2015.09 Oct 6, 2015
@zhenlan zhenlan assigned hongdai and unassigned mconnew Nov 3, 2015
@hongdai
Copy link
Contributor

hongdai commented Nov 3, 2015

E2E tests are passing in the lab.

@hongdai hongdai closed this as completed Nov 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hongdai hongdai

Labels
None yet
Projects
None yet
Milestone
2015.10
Development

No branches or pull requests
4 participants
@iamjasonp @hongdai @mconnew @zhenlan