Fires when user wants to authenticate to the server.

Private Sub object_LoginPassword(User, Login, Password, Action)

The LoginPassword Event syntax has these parts:

The settings for Action are:

Constant		Value	Description
	Deny	0	Deny execution of the action.
	Allow	1	Allow to execute action.
	SilentDeny	2	Silently deny execution of the action.
	SilentAllow	3	Silently allow to execute action.

LoginPassword event is fired when the client tries to authenticate with the server using his Login and Password. At this point, you should test these values against one stored in your code (or your database of users), and set Action argument accordingly. So, if you find that user provided valid Login and Password - set Action = Allow. If he didn't provide valid information, set Action = Deny. wodFTPServer will allow 3 attempts for the client to login before he gets disconnected.

You can also set User.UseNTAuthentication property to True, so the client's credentials are validated by your NT system, not by yourself. Or, you can change Login and Password properties from within LoginPassword event code, and send them 'faked' to NT validation. This is your choice.

Even if you set Action = Allow, doesn't mean client is authenticated immediately. Still, it's possible that you set Authentication property to require both the password and the certificate - in which case wodFTPServer will wait for certificate information as well. You should wait for Connected event when user finally manages to connect.