We use the sFTP key exchange system almost exclusively.

Confirming what Jack writes below plus . . .

We are running sFTP connections for many trading partners throughout the day on a given system.

Every partner has different requirements and so we employ a unique userid per partner.

When the CL driver script enters *IX world it lands in the /home/<userid> directory on the IFS.

From there we an manage unique .sh and .py scripts sculpted for each partner's requirements.

So, for us, it is important to have unique profile per each sFTP partner.

Regards,

Jerry

On 12/21/2023 4:21 AM, Jack Woehr via MIDRANGE-L wrote:
When SFTPing to a remote system, all that matters is that you know an
account name at the remote end and you can either provide its password or
have a public key installed on the remote. It doesn't care who you are to
your local system.

The public key on the remote site must correspond to a private key found
either in the local user's ~/.ssh directory or pointed to by the
appropriate command line switch passed to the sftp command.

On Wed, Dec 20, 2023, 21:11 Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I need to set up a sFTP file transfer.

I have been provided a user name and password, the user is admin

I used the ssh -T admin@<hostname> to add the site to the known hosts
file.

Does the user profile name on the IBMi need to be the same or can I use a
user name of SFTPUSER or something similar with a maximum length of 8
characters ?

As an example can I log in as SFTPUSER (or change the current active
profile to SFTPUSER) and then use sftp admin@<hostname>

I thought this was fine but I just can't find an explicit answer.

Thank you

Don





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.