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

Scenarios attempting to use S.Security.Principal.WindowsIdentity.GetCurrent fail #946

Closed
iamjasonp opened this issue Mar 30, 2016 · 3 comments
Assignees
Labels
bug This is a product bug.
Milestone

Comments

@iamjasonp
Copy link
Member

We need to spend some time investigating the following security tests on Linux

Fails always:

   HttpsTests.ClientCertificate_EchoString [FAIL]
   HttpsTests.ServerCertificateValidation_EchoString [FAIL]
   Https_ClientCredentialTypeTests.NtlmAuthentication_RoundTrips_Echo [FAIL]
   Https_ClientCredentialTypeTests.WindowsAuthentication_RoundTrips_Echo [FAIL]
   NegotiateStream_Http_Tests.NegotiateStream_Http_AmbientCredentials [FAIL]

These seem to stem from the following callstack:

      Exception: System.PlatformNotSupportedException: Operation is not supported on this platform.
         at System.Security.Principal.WindowsIdentity.GetCurrent()

Investigate why using an ambient credential for Windows auth can work in tcp but not for http.

@iamjasonp
Copy link
Member Author

For the moment, use the manual test guide: https://github.com/dotnet/wcf/blob/master/Documentation/manualtest-guide.md

@iamjasonp
Copy link
Member Author

System.Security.Principal.WindowsIdentity.GetCurrent() is currently not an API supported in CoreFx, so are expected to fail on all platforms except Desktop. dotnet/corefx#7325 is an issue tracking a solution to the issue.

(Note: no matter what, we will need to look at the manual test guide for this - #946

@zhenlan zhenlan modified the milestones: 2016.05, 2016.04 May 10, 2016
@zhenlan zhenlan modified the milestones: 2016.05, 1.0.0-rtm May 24, 2016
@iamjasonp iamjasonp changed the title Security.TransportSecurity.Tests in HTTP Fail in Linux Scenarios attempting to use S.Security.Principal.WindowsIdentity.GetCurrent fail Jun 8, 2016
@iamjasonp iamjasonp modified the milestones: 2016.06, 1.0.0-rtm Jun 10, 2016
@zhenlan zhenlan modified the milestones: 2016.06, 2016.07 Jun 27, 2016
@zhenlan zhenlan modified the milestones: 2016.07, 2016.08 Aug 2, 2016
@zhenlan zhenlan modified the milestones: 2016.08, 2016.09 Aug 30, 2016
@zhenlan
Copy link
Member

zhenlan commented Jan 31, 2017

This issue has been worked around by #1569. However, the scenario still does not work E2E and it is tracked by #1589.

@zhenlan zhenlan closed this as completed Jan 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This is a product bug.
Projects
None yet
Development

No branches or pull requests

3 participants