Back to product page
- Introduction
- License agreement
- Classes
- Enumerations
- Exceptions
- WeOnlyDo.Client.FtpDLX
- Properties
- Authentication
- Blocking
- BufferSize
- Certificate
- Compression
- DirFormat
- DirItems
- Encryption
- Hostname
- KeepAlive
- LastError
- ListItem
- ListParams
- LocalPath
- Login
- MaxTransferRate
- Passive
- Password
- Port
- PreserveDates
- PrivateKey
- Protocol
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- PublicKeyOpenSSH
- PublicKeySSH
- RemotePath
- Resume
- SecureMethod
- SmartGet
- SmartPut
- State
- StrictHost
- Tag
- Timeout
- Timezone
- TransferMode
- TransferRate
- TransferTime
- UseIPv6
- Version
- Methods
- Events
- Properties
- WeOnlyDo.Client.DirItemsCollection
- WeOnlyDo.Client.DirItem
- How to get support?
Certificate property
Holds certificate for SSL authentication.
Type
ObjectSyntax
- C#
- VB.NET
Object Certificate {get; set; };
Property Certificate As Object
Remarks
Certificate property sets and returns object that represents the certificate that will be used with authentication. You must setup Authentication property prior to authenticating with your certificate/privatekey combination.It is used only for FTPS (or FTPSwithdata/FTPSimplicit) protocols:
wodFtpDLX.NET will check if PrivateKey matches provided Certificate before it tries to connect. If key is valid, it will try to authenticate on SSL level with the server. Usually, if server accepts the authentication, it will not even ask for a password.
wodFtpDLX.NET will in Certificate property accept:
- X509Certificate2 class containing certificate data. Since X509Certificate2 does have PrivateKey member, wodFtpDLX.NET will try to use this member directly for setting up your private key. If PrivateKey member is null, wodFtpDLX.NET will require you to set up PrivateKey property as well when using Certificate authentication.
- X509Certificate class containing certificate data. Make sure you set up PrivateKey property separately.