Re: Certificate Question for iSeries

[DrFranken <midrange@xxxxxxxxxxxx>]

The short answer is:  secrureftp.xxx.com is NOT equal to 
secrureftpa.xxx.com (and it's not spelled very nice either!) Therefore 
the certificate won't match that name and you'll get an error.  Now you 
COULD add a hosts table entry on both the test server as well as the pc 
used to test that points the secrureftp.xxx.com to the test server. Then 
you could test with the correct name and that would work.

The certificate is issued to that name not to a physical box.

 - Larry "DrFranken" Bolhuis

On 2/7/2011 3:25 PM, Lowary, Jim wrote:
> We have a vendor that has sent us a Certificate that is working fine.
>
> In the Certification Path it lists:
> VeriSign
>     Thawte
>        secrureftp.xxx.com
>
> In that hierarchical order.  This btw is for attaching to their
> production system.
>
> Come to find out they now want us to "test" on a test system which has
> the URL of:
> secrureftpa.xxx.com  (note the added "a" after ftp).  Well our iSeries
> does not like this
> and even if I use a PC Client it wants me to accept the
> secrureftpa.xxx.com, before
> attaching.
>
> I don't know all that much about certificates but if they are sending
> this to me from another
> URL wouldn't  they need another certificate or at least somehow include
> that URL in the Cert
> Path??
>
> This seems reasonable to me, but since I'm not that well versed on this
>   (I can barely stumble my way thru with help) I thought I'd better ask.
>
> Thanks
> -- Jim Lowary