Differences
This shows you the differences between the selected revisions of the page.
| ui_login 2023-02-09 | ui_login 2024-09-24 (current) | ||
| Line 9: | Line 9: | ||
| ===== [[new_site]] New Site ===== | ===== [[new_site]] New Site ===== | ||
| - | To connect to a new site, select //New Site// node in the tree on the left. Then select [[protocols|protocol]], enter hostname and your user name. Typically you will also need to enter your password. For details see below. | + | To connect to a new site, select //New Site// node in the tree on the left. Then select [[protocols|protocol]], enter host name and your user name. Typically you will also need to enter your password. For details see below. |
| To start ad-hoc connection, click //Login// button. | To start ad-hoc connection, click //Login// button. | ||
| Line 21: | Line 21: | ||
| The //File protocol// selection lets you choose [[protocols|transfer protocol]]. | The //File protocol// selection lets you choose [[protocols|transfer protocol]]. | ||
| - | When [[ftp|FTP protocol]] is selected, you can further specify to use basic unsecured variant (//No encryption//) or one of [[ftps#methods|methods to invoke FTPS]]. When [[webdav|WebDAV protocol]] is selected, you can choose between basic unsecured variant and secure one. | + | When [[ftp|FTP protocol]] is selected, you can further specify to use basic unsecured variant (//No ==encryption==//) or one of [[ftps#methods|methods to invoke FTPS]]. When [[webdav|WebDAV]] or [[s3|S3]] protocol is selected, you can choose between basic unsecured variant and secure one.((With the S3 protocol, selecting the unsecure variant makes sense only, when connecting to 3rd party S3 server, as Amazon S3 does not support unsecure connections.)) |
| - | The //Host name// box is where you type the name, or the IP address, of the server you want to connect to. //Host name// is the only mandatory box that must be filled for a session to open. You can use environment variables in the value with syntax ''%NAME%''. | + | The //Host name// box is where you type the name, or the IP address, of the server you want to connect to. //Host name// is the only mandatory box that must be filled for a session to open. You can use environment variables in the value with syntax ''%NAME%''. If you enter a [[session_url|session URL]] here, it will be parsed. |
| The //Port number// box lets you specify which port number on the server to connect to. You need to specify it only in rare circumstances, when the server uses non standard protocol.((SSH protocol uses port number 22 by default. FTP protocol uses port number 21 by default. [[ftps|FTPS]] protocol with implicit encryption uses port number 990 by default. WebDAV protocol uses port number 80 by default. Secure WebDAV and Amazon S3 use port 443.)) Otherwise WinSCP selects the standard port number for you. | The //Port number// box lets you specify which port number on the server to connect to. You need to specify it only in rare circumstances, when the server uses non standard protocol.((SSH protocol uses port number 22 by default. FTP protocol uses port number 21 by default. [[ftps|FTPS]] protocol with implicit encryption uses port number 990 by default. WebDAV protocol uses port number 80 by default. Secure WebDAV and Amazon S3 use port 443.)) Otherwise WinSCP selects the standard port number for you. | ||
| - | The //Username// box is where you type your account name on the server. If you do not fill the username, you will be [[ui_authenticate#username|prompted for username]] then.((Except for special scenarios, such as authentication-less connection or [[ui_login_authentication#gssapi|GSSAPI authentication]].)) You can use environment variables in the value with syntax ''%NAME%''. For Amazon S3, use //[[guide_amazon_s3#connecting|Access key ID]]//. | + | The //User name// box is where you type your account name on the server. If you do not fill the username, you will be [[ui_authenticate#username|prompted for username]] then.((Except for special scenarios, such as authentication-less connection or [[ui_login_authentication#gssapi|GSSAPI authentication]].)) You can use environment variables in the value with syntax ''%NAME%''. For Amazon S3, use //[[guide_amazon_s3#connecting|Access key ID]]//. |
| The //Password// box is for the password associated with the account. You are advised not to fill it in if you are going to [[session_configuration#site|save the site]]. If you decide to do so nevertheless, do not forget to force password storing on the //[[ui_login_save|Save session as dialog]]//. Also do not fill the password if you are going to use other [[ssh#authentication|authentication method]] (like public key). If you do not fill the password and other authentication methods fail (password authentication has the lowest preference), you will be [[ui_authenticate#password|prompted for password]] then. For Amazon %%S3%%, use //[[guide_amazon_s3#connecting|Secret access key]]//. | The //Password// box is for the password associated with the account. You are advised not to fill it in if you are going to [[session_configuration#site|save the site]]. If you decide to do so nevertheless, do not forget to force password storing on the //[[ui_login_save|Save session as dialog]]//. Also do not fill the password if you are going to use other [[ssh#authentication|authentication method]] (like public key). If you do not fill the password and other authentication methods fail (password authentication has the lowest preference), you will be [[ui_authenticate#password|prompted for password]] then. For Amazon %%S3%%, use //[[guide_amazon_s3#connecting|Secret access key]]//. | ||
| Line 33: | Line 33: | ||
| With [[ftp|FTP protocol]] you can use //Anonymous login//. It effectively sets the //User name// to ''anonymous'' and //Password// to ''anonymous@example.com''. | With [[ftp|FTP protocol]] you can use //Anonymous login//. It effectively sets the //User name// to ''anonymous'' and //Password// to ''anonymous@example.com''. | ||
| - | With [[s3|S3 protocol]] you can //==Read credentials== from %%AWS%% CLI configuration//. The discovered credentials will be show in the respective boxes, but they won't be saved. They will be read again each time you login. The ''AWS_ACCESS_KEY_ID'', ''AWS_SECRET_ACCESS_KEY'', ''AWS_SESSION_TOKEN'', ''AWS_CONFIG_FILE'' and ''AWS_PROFILE'' environment variables and the default ''.aws\credentials'' configuration file are used in the same order as AWS tools do. | + | With [[s3|S3 protocol]] you can use ==?read_credentials== //Credentials from %%AWS%% environment//. The discovered credentials will show in the respective boxes, but they won't be saved. They will be read again each time you login. The IAM role, ''AWS_ACCESS_KEY_ID'', ''AWS_SECRET_ACCESS_KEY'', ''AWS_SESSION_TOKEN'', ''AWS_CONFIG_FILE'', ''AWS_PROFILE'' and ''AWS_SHARED_CREDENTIALS_FILE'' //(latest beta version only)// &beta environment variables and the profiles in the default ''.aws\credentials'' and ''.aws\config'' //(beta only)// &beta configuration files are used in the same order as AWS tools do. You can choose specific profile in combo box next to the checkbox. |
| If you need to configure advanced settings, click //Advanced// button to open [[ui_login_advanced|Advanced Site Settings dialog]]. For settings not directly available in the interface and other special needs, use //Advanced > Edit Raw Settings// command to open [[ui_login_raw|Raw Site Settings dialog]]. For configuring [[transfer_settings#presets|transfer settings preset]] for the site, use //Advanced > Transfer Settings Rule// to open [[ui_transfer_preset|Transfer Settings Preset editor]]. | If you need to configure advanced settings, click //Advanced// button to open [[ui_login_advanced|Advanced Site Settings dialog]]. For settings not directly available in the interface and other special needs, use //Advanced > Edit Raw Settings// command to open [[ui_login_raw|Raw Site Settings dialog]]. For configuring [[transfer_settings#presets|transfer settings preset]] for the site, use //Advanced > Transfer Settings Rule// to open [[ui_transfer_preset|Transfer Settings Preset editor]]. | ||
| Line 79: | Line 79: | ||
| ==== [[opening_in_putty]] Opening Site in PuTTY ==== | ==== [[opening_in_putty]] Opening Site in PuTTY ==== | ||
| - | You can open configured session, the selected site or all sites in the selected folder (&beta_feature) in [[integration_putty#open_putty_new|PuTTY SSH client]] instead of WinSCP. Use //Manage > Open in PuTTY// command.((Hold down ''Shift'' key to open the site in PuTTY without closing WinSCP Login dialog.)) | + | You can open configured session, the selected site or all sites in the selected folder in [[integration_putty#open_putty_new|PuTTY SSH client]] instead of WinSCP. Use //Manage > Open in PuTTY// command.((Hold down ''Shift'' key to open the site in PuTTY without closing WinSCP Login dialog.)) |
| + | |||
| + | Opening sessions that require an SSH tunnel is not possible this way. You have to first open the session with the tunnel in WinSCP and only then open the session in PuTTY. | ||
| ==== [[defaults]] Default Session Settings ==== | ==== [[defaults]] Default Session Settings ==== | ||