Hi Dave.
Does the password have special characters? I faced a similar situation, and
the solution was to use the RAW function (
http://camel.apache.org/how-do-i-configure-password-options-on-camel-endpoints-without-the-value-being-encoded.html)
in the password.
Abraços,
Luis Felipe - Finx
On Fri, Mar 3, 2017 at 11:52 PM, David Hoffer <dhoff...@gmail.com> wrote:
> We are using password authentication
>
> We have log4j configured but aren't seeing any connection handshake log
> messages with debug enabled but I'm not sure what JSCH (the actual
> connection library) has for logging.
>
> Our situation is we have an SFTP server that we have no control over that
> is refusing to connect with Camel. However we can connect with fsftp
> fine. SSH is disabled so cannot connect with putty. However when we setup
> a similar linux server locally camel connects to it just fine. We are
> trying to figure out why it fails for this one connection we have no
> control or system information of (e.g. we can't get on the box that is
> failing to accept our connection and check logs/etc).
>
> -Dave
>
> On Fri, Mar 3, 2017 at 5:41 PM, S AR <sa_remin...@hotmail.com> wrote:
>
> > What errors do you receive?
> >
> > Are you using password authentication or privateKey authentication?
> >
> > If you are using privateKey, Have you generated a private key file?
> >
> > Regarding logging, since camel uses log4j2, you can configure an appender
> > for the classes in the package: org.apache.camel.component.file
> >
> > In log4j2, that means, you should have something like this:
> >
> > appender.mylogger.type = Console
> > appender.mylogger.name = MYLOGGER
> > appender.mylogger.layout.type = PatternLayout
> > appender.mylogger.layout.pattern = %d %p %C{1.} [%t] %m%n
> >
> > logger.mylogger.name = org.apache.camel.component.file
> > logger.mylogger.level = debug
> > logger.mylogger.additivity = false
> > logger.mylogger.appenderRef.mylogger.ref = MYLOGGER
> >
> > Regards.
> >
> > On 03.03.2017 18:16, David Hoffer wrote:
> >
> > Is there a way to turn on low level logging so we can see why Camel is
> > failing to connect? We can connect to the same server with puttyftp and
> > put files but not with camel...and the errors are not very detailed.
> >
> > -Dave
> >
> > On Fri, Mar 3, 2017 at 9:54 AM, S AR <sa_remin...@hotmail.com><mailto:
> > sa_remin...@hotmail.com> wrote:
> >
> >
> >
> > Hello David,
> >
> > When I work with camel-sftp, The first thing I do is to manually connect
> > to the remote machine via ssh, so that my knownHosts
> > (System.getProperty(user.home)/.ssh/known_hosts) file is written. On
> > windows, I use cygwin for that. I assume you can do the same with putty.
> >
> >
> > You specify the certificate file as an option, as described in the
> > documentation: http://camel.apache.org/ftp2.html
> >
> > knownHostFile: path to your known_hosts
> >
> > privateKeyFile: path to your id_rsa
> >
> >
> > privateKeyFilePassphrase: passphrase of you id_rsa
> >
> >
> > Hope it gives you an idea about where to look at.
> >
> >
> > Good luck.
> >
> >
> > On 03.03.2017 17:32, David Hoffer wrote:
> >
> > How does Camel handle the SSH cert when connecting to SFTP servers?
> > Somehow it has to accept the cert provided by the server how does it do
> > that?
> >
> > The docs say the default is:
> > strictHostKeyChecking=no
> >
> > What does this mean? Does this mean it will accept every cert?
> >
> > What does strictHostKeyChecking=yes mean?
> >
> > Where does Camel store the cert that it accepted? Can we preempt this
> hole
> > process by manually accepting the cert with a different tool, eg.
> > puttyftp? In this case there would have to be a shared location for the
> > cert...we are running camel on Windows so I think puttyftp stores the
> cert
> > in the registry. Where does Camel/JSCH look for certs?
> >
> > -Dave
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
