let working = {
foo: function() {
console.log("working");
}
};
let notworking = {
foo() {
console.log("notworking");
}
}
new working.foo();
new notworking.foo();
and its output
Uncaught TypeError: notworking.foo is not a constructorplease explain why this particular function cannot be used as a constructor function.
Hint: based on this SO question where the explanation is provided.
var principalContext = new PrincipalContext(ContextType.Domain, domain); principalContext.ValidateCredentials(username, password);And this is where the problem is.
|
I am using PrincipalContext.ValidateCredentials(string, string) to validate user credentials. I am encountering behaviour that I am unable to explain and have, so far, been unable to clarify through usual searches and forum visits. Here is the behaviour, the credentials can be assumed to be correct on each call. The non-SSL behaviour is what I would expect. The SSL behaviour is not as expected in my understanding of the method.
Not using SSL/TLS
User is enabled and NOT expired - method returns TRUE User is disabled and NOT expired - method returns FALSE User is enabled and EXPIRED - method returns FALSE User is disabled and EXPIRED - Method returns FALSE
Using SSL/TLS
To summarise - when both machines in the negotiation (app server and domain controller) have the required certs installed, they will use SSL (port 636). In these circumstances the method returns TRUE for Expired accounts but when not using SSL (port 389) (for example the app server does not have the cert installed) the method is returning FALSE for Expired accounts.
I would expect the return value to be the same for expired accounts in both scenarios, but it's possible I'm not considering something.
User is enabled and NOT expired - method returns TRUE User is disabled and NOT expired - method returns FALSE User is enabled and EXPIRED - method returns TRUE User is disabled and EXPIRED - Method returns FALSE |
| Here's how ValidateCredentials(string, string) works: First, it tries to authenticate with the Negotiate, Signing, and Sealing context options. If this fails, it tries again with SimpleBind and SecureSocketLayer. |
var principalContext = new PrincipalContext(ContextType.Domain, domain); principalContext.ValidateCredentials(username, password);just make sure you call it
var principalContext = new PrincipalContext(ContextType.Domain, domain, ContextOptions.Negotiate | ContextOptions.Sealing | ContextOptions.Signing); principalContext.ValidateCredentials(username, password);This makes sure there's no SimpleBind+SSL fallback as it forces Kerberos only. And guess what? It just works correctly. Expired passwords are no longer accepted.
public interface IDoSomething: IDisposable { }
class DoesSomething<String> : IDoSomething<String>
{
public void Dispose()
{
}
}
class DoesSomething<string> : IDoSomething<string>
{
public void Dispose()
{
}
}
Posts
All Comments
