LogonUser can be too slow - looking for a way to authenticate the user only locally, or reduce the central validation timeout

Asked Dec 10 '12 at 13:05

Active Oct 19 '20 at 10:25

Viewed 926 times

I'm having trouble finding a quick way to authenticate users. LogonUser takes several seconds to return when a connection to the domain controller is slow or not available.

I'm using LOGON32_LOGON_NETWORK as the logon type, which I've read it's faster, but the function still takes several seconds to return on those occasions. I assume it's the server timeout before resorting to the cached credentials.

Since I don't want/need the domain validation:

is there any way to reduce the timeout before using the cached credentials?
is there any way to authenticate only locally (without checking with the domain controller at all)?
are there other ways to authenticate the logged-on user that are faster?

asked Dec 10 '12 at 13:05

baderous

2

You are out of luck. If you want to authenticate a domain user, you can't avoid this. If you want to authenticate to a local user, go right ahead and do that. – David Heffernan Dec 10 '12 at 13:16
@DavidHeffernan Thanks! But if the logged-on user is a domain user, is it possible to authenticate him *only locally*, using LogonUser? If so, how? – baderous Dec 10 '12 at 13:53
2

No it's not. You'd need to make a special local user for this purpose. – David Heffernan Dec 10 '12 at 13:58
I wish I could downvote my corporate server. – djv Apr 15 '15 at 20:57

LogonUser can be too slow - looking for a way to authenticate the user only locally, or reduce the central validation timeout

0 Answers0