Back to product page
- Introduction
- Overview
- License agreement
- Getting Started
- Objects
- Enumerations
- wodFTPD
- Methods
- Properties
- Authentication
- BindIP
- BindIPType
- Certificate
- DirFormat
- Encryption
- EncryptionList
- FileLocking
- FIPS
- ForceUTF8
- GoodbyeMessage
- GreetingMessage
- HMacList
- HostKeyList
- KeyExchangeList
- MaxDataPort
- MinDataPort
- MonitorTransfers
- MyHostname
- MyIP
- Notification
- PasvPort
- Port
- Protocol
- Secure
- ServerName
- SFTPVersion
- Status
- StrictDataIP
- Threads
- Timeout
- UseIPv6
- Users
- Version
- VirtualFiles
- VirtualFolders
- Events
- wodFTPDNotify
- FtpUser
- FtpUsers
- VirtualFile
- VirtualFiles
- VirtualFolder
- VirtualFolders
- How to get support?
- Technical information
- Fast notifications interface
- Error list
LoginPassword notification
Called when user wants to authenticate to the server.
Syntax
- Basic
object.LoginPassword Owner, User, Login, Password, Action
The LoginPassword(object,Owner,User,Login,Password,Action) syntax has these parts:
The LoginPassword(object,Owner,User,Login,Password,Action) syntax has these parts:
object | An expression evaluating to an object of type wodFTPDNotify. |
Owner | A wodFTPDCom object. Reference to wodFTPServer instance that called this notification method. |
User | A FtpUser object. Reference to user who provided his login and password. |
Login | A String value. Holds login/username user provided. |
Password | A String value. Holds password user provided. |
Action | A FtpActions enumeration, as described in settings. When set to Deny/SilentDeny, wodFTPServer denies this action. |
Remarks
NOTE: This method is called only if you implemented IwodFTPDNotify interface in your application, and wodFTPD.Notification property has received reference to instance of your implementation.LoginPassword notification method is called 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 notification when user finally manages to connect.
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. |