Re: initiating ftp from IBM i to another place but with a certificate

Rob,

Brad is right that unless you're doing client authentication you won't need to provide a certificate on the FTP client side. You will know you are if the certificate file sent to you is password protected. It would probably be a .p12 file. In this case you will need to load it and create a new application id that references it. You will use this id on the FTP command. If however this is an FTPs session then you need to import the CA chain. You don't need to worry about linking it to your FTP client - as long as the FTP server presents you with a certificate that's loaded then all is ok.

Tim


On 4/21/2016 4:32 PM, Bradley Stone wrote:

Rob,

Are you SURE you need to be using a client side certificate? It's very
rare for clients to use them.

If you do, then I sent instructions on how to set up an application ID and
assign it to a certificate (not a CA) that you imported and how to find the
application name here:

http://www.fieldexit.com/forum/display?threadid=297

Yes, this is for GETURI, but a client is a client. :)

Brad
www.bvstools.com

On Thu, Apr 21, 2016 at 9:29 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

I'll be honest. At first I was thinking that there was a serious
breakdown in communication and I was going to have to explain this all to
you from the ground up. But I decided to actually listen to you and try
what you said.
So I went into Manage Applications.
Then I selected View application definition.
I selected Client.
And I saw that we already had "IBM i TCP/IP FTP Client". At first I was
thinking "hey I was right! There is already this application we should be
using." Then I noticed that we played with this further down and had a
different application "Ourcustomer Web Services".
So I viewed that.
- It has it's own Application ID.
- It has it's own certificate assigned to it.
So, I should record all the values for "IBM i TCP/IP FTP Client", create a
new application and intelligently use most of the same parameters as were
on "IBM i TCP/IP FTP Client" but change the necessary ones for our new
application id.

Right?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Tim Bronski <tim.bronski@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/21/2016 10:19 AM
Subject: Re: initiating ftp from IBM i to another place but with a
certificate
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I could have been a little clearer,

In DCM select the *SYSTEM store and you should see manage applications.
From here you can add a client one. You just need a name and
description. Once it's created you can update it and assign a
certificate. It's just a handle for a certificate.



On 4/21/2016 2:59 PM, Rob Berendt wrote:

So, in DCM, when you view the certificate, and you see:
Certificate Common name
Mycustomer EDI VN123456

Is the APPID the "Common name"?

--
Need sFTP or PGP? Download your native sFTP or OpenPGP solutions here:
www.arpeggiosoftware.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.