RE: Setting Up sFTP for a Second Vendor - Host key

There is no reason why a key pair can't work with multiple vendors, or
for different users if you have it loaded correctly, and based on the
steps you took, you appear to have it set up correctly on your side. It
is up to the server operator to see what is going wrong now.

Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Adams, Jay
Sent: Thursday, May 10, 2018 8:33 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Setting Up sFTP for a Second Vendor - Host key

Thanks to both Kevins for responding and thanks for being patient with

me. I

am learning a lot going through this process.

You asked if I had sent them my public key. Yes. And just to be sure I

did this

correctly I will explain how I did it.
Several months ago I set up sFTP with another vendor.
At that time, I created my public and private ssh keys and put them

under

user BLUSER in directory /home/BLUSER/.ssh.
I assumed those ssh keys could be used for any vendor, so I copied

them

(id_rsa and id_rsa.pub) to /home/CCUSER/.ssh.
I emailed the id_rsa.pub key to the new vendor and they said they put

it on

their keyring.
The public key I created for the previous vendor can also be used for

this

new vendor, right?

------------------------------

message: 3
date: Wed, 9 May 2018 07:21:01 -0500
from: "Kevin Bucknum" <Kevin@xxxxxxxxxxxxxxxxxxx>
subject: RE: Setting Up sFTP for a Second Vendor - Host key

The lines you are highlighting indicate that it connected, and that

you trust

that st.concursolutions.com are who they say they are (you have

trusted

their host key). After that I moves on to proving that you are who you

say

you are. It says that it can take passwords or public keys.
Your side offers the id_rsa public key, and the other side immediately

comes

back and asks again for something different. That means that the issue

is on

the other side now. They either don't have your public key loaded (

you did

give it to them correct? ) or they have some other config issue on

that side.

You could try and connect with two v's sftp -vv and see if the extra

debug

gives some more information, but most likely someone at
concursolutions.com will have to look at their logs and config and see

what is

happening.