...
Using the SFTP tab from the Profile Window shows the following tab window:
A user name has to be specified independently from the authentication methods to be used.
| Note |
|---|
Keep in mind that all authentication methods have to be enabled accordingly with the SSH server in use. If in doubt contact your system administrator to check respective settings in sshd_config and related files. |
...
- You have to specify both Public / Private Key and one of the Password related authentication methods.
- JOE will send forward the private key and the password to the SSH server and both authentication methods have to match.
Which password related authentication method has to be be used (Password, or Keyboard Interactive) depends on the SSH server settings.
...
- You can specify any of the authentication methods Public / Private Key, Password or Keyboard Interactive provided that the authentication method is enabled with the SSH server.
- Should the SSH server be configured to allow a number of alternative authentication methods then the following behavior applies:
- JOE will try to use Private / Public Key authentication and then Password authentication.
- If the private key matches then authentication is completed and no Password authentication takes placeis performed.
- Should Public / Private Key authentication fail but subsequent Password authentication be successful then the user is authenticated.
- You can specify none of the authentication methods Public / Private Key, Password or Keyboard Interactive. This configuration is used if the user account does not make use of a password, e.g. for anonymous access.
Public / Private Key related Authentication Methods
...
JOE forces interactive user input to type enter the password.
Use Passphrase stored with JOE
...
Password related Authentication Methods
Keyboard Interactive
...
This method indicates that the password has to be typed from the keyboard, it cannot be stored with JOE.
...
This method is not considered a secure way to handle passwords, however, for uncritical environments you might consider this a viable approach.
Logging
Starting from
| Display feature availability | ||
|---|---|---|
|
./lib/JOE-log4j.properties configuration file that looks like this, see | Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
log4j.rootLogger=error, stdout, joe
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=[%5p] (%F:%L) - %m%n
log4j.appender.joe=org.apache.log4j.FileAppender
log4j.appender.joe.Append=false
log4j.appender.joe.layout=org.apache.log4j.EnhancedPatternLayout
log4j.appender.joe.layout.ConversionPattern=%d{ISO8601}{Europe/Berlin} %c [%-5p] - %m%n
log4j.appender.joe.File=${SCHEDULER_DATA}/logs/JOE.log |
Explanations:
- Line 1: by default exclusively errors and output to stdout is logged.
- Modify this setting to "
debug, stdout, joe" to receive detailed debug information about SSH key exchange.
- Modify this setting to "
- Line 11: the location of the log file is the
./logsfolder of the JOE configuration directory.