SFTP Settings

[Jeff Anderson]

Has anyone ever run into an issue where you can send a file to a vendor via curl, but cannot get the settings on the CL tab to work?

The following command lines work (a couple of diff ways):

curl -v -k sftp://vendorip/dropFolder/file.hl7 –user “userid” -T file.hl7
curl -v -k –upload-file file.hl7 sftp://vendorip/dropfolder/file.hl7 –user “userid”

I can’t for the life of me get CL to work. I’ve opened a ticket with Infor and they are stumped as well. Any thoughts would be greatly appreciated.

On the FTP protocol tab I’ve got the user/password set. The outbound directory set. The style set to hl7 with the append data unchecked, and the host/port set up.

I have dozens of ftp’s working and this is the only one that is giving me fits.

Thank you in advance!

Jeff

Topic

[Jim Kosloskey]

Have you tried turning the noise level up (verbose) on the protocol to see if anything informative shows up in the log?

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 61 years IT – old fart.

[Ib H]

Hello,

I would sugges setting CURLOPT_VERBOSE to 1 in the cURL Options to make the logging more verbose as suggested.
Also to emulate the -k option for curl, try setting these 2 also :
CURLOPT_SSL_VERIFYHOST to 1
CURLOPT_SSL_VERIFYPEER to 1
Mind that this will be less secure.

Also check the ciphers on the destination and Cloverleaf and see if they match.
We have had some challenges with connection to servers where ciphers on the destination were newer/more secure than
the ciphers available on Cloverleaf 6.2

Yours sincerely

Ib Højme

[Jeff Anderson]

You’ll never believe the solution… Generally I can log in via FileZilla and pull the directory from that e.g.  “/somefolder” in this case it was “somefolder” the preceding “/” was causing the error, probably trying to change directory from the root level… weird I’ve never seen that issue before.

[Jason Russell]

There is an update in 2022.09.04 that helps deal with an issue with leading slashes and how Cloverleaf sends them via cURL. I’m not sure if that is the issue you’re experiencing (or if it’s a new or unknown server):

<td width=”600″>This enhancement introduces a configurable system variable that allows users to determine how the leading slash and special characters in SFTP absolute paths are encoded when connecting to SFTP servers. Previously, the system always encoded both the leading slash and special characters, which could cause compatibility issues with certain SFTP servers that do not support encoded leading slashes. With this update, users can select from four options:
0 (default): Both leading slash and special characters are encoded
1: Only special characters are encoded
2: Only the leading slash is encoded
3: Neither the leading slash nor special characters are encoded
This change provides greater flexibility and compatibility with a wider range of SFTP server implementations. No changes are required to existing configurations unless a different encoding behavior is desired. The new system variable can be set according to your environment’s requirements. No impact is expected on other programs, business classes, or extension processes. Infor has tested the new options to ensure correct path handling for all four settings. There are no dependencies or feature toggles associated with this enhancement.

[Author]

Replies