-
Notifications
You must be signed in to change notification settings - Fork 557
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
HTTP does not support UpnEndpointIdentity #10
Comments
With this, this should only be an issue for UWP. |
This is a little bit more nuanced:
|
Tests disabled with Issue(10) now pass for me on Windows when run manually. They fail on UWP, but I think PR #1502 will remove the PNSE and allow us to see if the tests pass in UWP. |
PR dotnet#1502 fixed issue dotnet#10 by implementing UpnEndpointIdentity. But 2 tests were still disabled by issue 10, so this PR just re-enables those tests. Both require manual setup to run, so we will not see them pass or fail in CI or VSO.
Reopening -- this issue exists only in UWP, even after PR #1502. |
PR dotnet#1502 fixed issue dotnet#10 by implementing UpnEndpointIdentity. But 2 tests were still disabled by issue 10, so this PR just re-enables those tests. Both require manual setup to run, so we will not see them pass or fail in CI or VSO. These tests still fail in UWP and so remain disabled there.
Fix UpnEndpointIdentity on UWP Re-enable tests disabled by issue 10, except for NET Native. PR dotnet#1502 fixed issue dotnet#10 by implementing UpnEndpointIdentity. But 2 tests were still disabled by issue 10, so this PR just re-enables those tests. Both require manual setup to run, so we will not see them pass or fail in CI or VSO. These tests still fail in UWP and so remain disabled there.
Fix UpnEndpointIdentity on UWP Re-enable tests disabled by issue 10, except for NET Native. PR dotnet#1502 fixed issue dotnet#10 by implementing UpnEndpointIdentity. But 2 tests were still disabled by issue 10, so this PR just re-enables those tests. Both require manual setup to run, so we will not see them pass or fail in CI or VSO. These tests still fail in UWP and so remain disabled there.
Retesting in UWP showed these tests pass now, so PR #1560 has been opened to re-enable them. |
Re-enable tests disabled in UWP for issue #10
Closing now that #1560 has been merged. I manually tested this against NET Native running against a self-hosted service running on a 2nd machine, and passing explicit credential in TestProperties. |
The ctor currently throws PlatformNotSupportedException
The text was updated successfully, but these errors were encountered: