Back to product page
- Introduction
- License agreement
- Getting Started
- Enumerations
- Objects
- wodTelnetDLX
- Methods
- Properties
- Authentication
- AutoSize
- BackColor
- BackLog
- BindIP
- BindPort
- Blocking
- BorderVisible
- Certificate
- CharEncoding
- Column
- Columns
- ColWidth
- Command
- ContextMenu
- CursorHeight
- DataOut
- DataReady
- Enabled
- ErrorText
- ExitSignal
- ExitStatus
- Font
- ForeColor
- HandleSysKeys
- Hostname
- hWnd
- KeepAlives
- Language
- LastError
- LocalCertBag
- Login
- MousePointer
- MouseWheel
- MyHostname
- MyIP
- Notification
- Password
- Picture
- Port
- Prompt
- Protocol
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- RecordMode
- RemoteIdentification
- Row
- RowHeight
- Rows
- ScrollBars
- ScrollX
- ScrollY
- SecureMethod
- SelectedText
- ShowCursor
- Socket
- SpecialKeyFocus
- State
- StateText
- StripANSI
- StripColors
- TabStop
- TelnetOption
- TerminalEmulation
- TerminalType
- Text
- Timeout
- TranslateSpecial
- UseIPv6
- Version
- Events
- IwodTelnetNotify
- wodTelnetDLX
- How to get support?
- Technical information
- Fast notifications interface
- Error list
Authentication property
Determines which authentication type is used.
Type
AuthenticationsEnum enumeration.Syntax
- Basic
object.Authentication [= value]
The Authentication(object) syntax has these parts:
The Authentication(object) syntax has these parts:
object | An expression evaluating to an object of type wodTelnetDLX |
Remarks
Authentication property allows you to select type of authentication you want to use with the server. Most commonly, you will choose authPassword authentication, which requires Login and Password properties to be set before Connect method is called. Once wodTelnetDLX connects to the server, it will authenticate you ONLY with username and password.If you prefer to authenticate yourself using your PrivateKey (server MUST have your public key in that case), you should set this property to authCertificate, and you should set Login and Certificate properties accordingly.
If you're using SSH protocols, then Certificate property must hold at least Private key - no matter if you generated it or loaded it. If SSL protocols are used, you must load or generate also valid certificate that is sent to the client. If you allow any of above (Password and Certificate/Key) authentications to take place, set this property to authBoth value. In this case wodTelnetDLX will try to use both methods.
Different server implementations may require either one or both of the authentications are successful to login to the server. Please note that in this case you must set all three properties: Login, Password and Certificate.
wodTelnetDLX also supports NTLM authentication. For this, both Login and Password must be set prior to calling Connect method.
To set Certificate, use Certificate Management object (included in the setup package) that will allow you to generate (and store) required keys and certificates.