Determines which authentication type is to be used.

An AuthenticationsEnum enumeration.  Determines authentication type.

object.Authentication [= value]

The Authentication Property syntax has these parts:

The settings for value are:

Constant		Value	Description
	authBoth	0	Use both authentication methods.
	authPassword	1	Use password authentication.
	authPubkey	2	Use public key authentication.
	authSecurID	3	Use SecurID token authentication
	authKeyboardInteractive	4	Use KeyboardInteractive authentication
	authGSSAPI	5	Use Kerberos GSS authentication

The Authentication property allows you to select the type of authentication that you want to use with the server. Most commonly, you will choose authPassword authentication, which requires you to set the Login and Password properties before the Connect method is called. Once wodSSH connects to the server it will authenticate you ONLY with username and password.

If you prefer to authenticate yourself using your PrivateKey (in which case the server MUST have your public key), you should set this property to authPubkey and you should set the Login and PrivateKey properties accordingly.

If you want to allow any of these types of authentication to take place, set this property to authBoth. In this case wodSSH will try to use both methods. Different server implementations may require that either one or both of the authentication methods are successful in order to login to the server. Please note that in this case you must set all three properties: Login, Password and PrivateKey.

To set PrivateKey, use the Keys object (included in the setup package) this will allow you to generate (and store) the required keys.

You can also use authSecurID authentication. In this case, set your Login, and instead of your password, provide the OTP (one time password) as provided by your token. wodSSH will send authentication information to the server using these properties. Obviously, in this case you cannot use Password at the same time.

wodSSH also supports keyboard-interactive authentication. As a fallback method wodSSH will attempt to authenticate using this method if Password authentication fails.

authGSSAPI implements Kerberos protocol (http://web.mit.edu/Kerberos). When this authentication is used, there is no need to provide Login and Password at all - they are requested from the Kerberos authority (assuming you have valid credentials) and authentication is made without providing any login details in the code. wodSSH supports both SSPI (Microsoft implementation) and KfW (MIT open source) implementations - whichever is available on the local system.