Testing a `PrincipalContext` using `ValidateCredentials(null, null)` behaves unexpectedly

debugcn 投稿 Dev

Wes Toleman

I need to validate the credentials that are used to connect to an AD server. If if pass invalid credentials to PrincipalContext(ContextType, String, String, String), PrincipalContext.ConnectedServer throws a System.DirectoryServices.DirectoryServicesCOMException which is discovered on the first use of the PrincipalContext.

I am trying to test the credentials with PrincipalContext.ValidateCredentials(null, null) but I am having issues. According to the .NET Core 2.0 docs

The ValidateCredentials method binds to the server specified in the constructor. If the username and password parameters are null, the credentials specified in the constructor are validated.

I create a connnection to the server.

string username = "username"
string password = "password"

PrincipalContext ctx = new PrincipalContext(ContextType.Domain, "my_domain.local", username, password);

And then to test the connection I try:

if (ctx.ValidateCredentials(null, null))
{
    // This block does not get hit!
    // This is surprising because the credentials are valid
}

Which has different behaviour to:

if (ctx.ValidateCredentials(username, password))
{
    // Credentials are valid, this block gets hit
}

The docs lead me to believe these calls should behave identically yet I am experiencing different results. Why is this and what is the proper way to test a connection?

Gabriel Luci

I was able to replicate this by running your code under a local account on my computer and passing valid domain credentials in the constructor. ValidateCredentials(null, null) does indeed fail.

This sounds like a bug, either in the code or in the documentation, so I've filed a bug on GitHub: https://github.com/dotnet/corefx/issues/29369

Edit: looks like they've decided to leave the implementation as-is and correct the documentation.

この記事はインターネットから収集されたものであり、転載の際にはソースを示してください。

侵害の場合は、連絡してください[email protected]

編集2021-06-3

コメントを追加

サインイン

分類Dev

Related 関連記事

記事

Testing a `PrincipalContext` using `ValidateCredentials(null, null)` behaves unexpectedly

Testing a `PrincipalContext` using `ValidateCredentials(null, null)` behaves unexpectedly

jsonschema - oneOf keyword behaves unexpectedly

Fragment shader behaves unexpectedly (Test grid)

Go concurrency with for loop and anonymous function behaves unexpectedly

Child fragment from onListItemClick within viewPager behaves unexpectedly

Using Fused Location API and App Crashing Unexpectedly

SqlConnection closes unexpectedly inside using statement

In Antlr4 enter listener, accessor function unexpectedly returns null

Using setTimeout() in React and Testing it

「ValidateCredentials（null、null）」を使用して「PrincipalContext」をテストすると、予期しない動作が発生します

Unexpectedly found nil when using variable outside of declared function

Unexpected null reference when testing with NUnit and Moq

Angular testing: Cannot read property 'nativeElement' of null

Testing default IFS against null IFS

Testing `instanceof` is redundant and can be replaced with `!= null`?

Testing Subject using TestScheduler in RxJs

Testing argument using Python Click

PrincipalContextのしくみ

Testing a controller not using $scope using karma

Detox partially visible Button behaves differently using toBeVisible() expectation and tap() action

Why does one of my two Dell monitors unexpectedly enter power save mode when using DisplayPort daisychaining?

Parameterized testing with Mockito by using JUnit @Rule?

Testing concrete methods in abstract classes using subclasses

Testing MVC controller using reactor with WebClient

Using queries with ORDER BY when testing with the embedded runtime

Using react-testing-library with storyshots?

Testing with Jest in Typescript using a Bazel custom rule

Testing functions with properties using Jest and Sinon

Jmeter load testing using single machine

Automated Testing using MS Coded UI